8000 Tags · j-sandy/front50 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: j-sandy/front50

Tags

version-0.27.1

Toggle version-0.27.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(build): release when tags matching version-[0-9]+.[0-9]+.[0-9]+… (

spinnaker#1039)

The jenkins jobs that publish/release spinnaker use tags of this form.  See e.g
https://github.com/spinnaker/buildtool/blob/d5ce1398e386c2ff92881310aba5a58f305b0241/dev/buildtool/spinnaker_commands.py#L295
+
https://github.com/spinnaker/buildtool/blob/d5ce1398e386c2ff92881310aba5a58f305b0241/dev/buildtool/spinnaker_commands.py#L305

Those jobs currently publish to bintray, but since that is going away, let's publish to nexus.

version-0.27.0

Toggle version-0.27.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(dependencies): Autobump korkVersion (spinnaker#1032)

Co-authored-by: root <root@3c2f555b53f9>

v2.23.0

Toggle v2.23.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(dependencies): Autobump korkVersion (spinnaker#1019)

Co-authored-by: root <root@ca927ee64684>

version-0.26.2

Toggle version-0.26.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(sql): Ensure that `Application.createTs` is reliably returned whe…

…n sql is used (spinnaker#1014)

For historical reasons, the original `createTs` value on the Application object itself
is not reliably stored.

When sql backends are used, the `created_at` column is the most accurate representation
of the time at which an Application was created.

This PR will override any `createTs` value that happens to exist in the Application
json blob with the value of the db column.

v2.22.0

Toggle v2.22.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(build): Stop publishing debians on release builds (spinnaker#1007)

version-0.26.1

Toggle version-0.26.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(dependencies): Autobump korkVersion (spinnaker#999)

Co-authored-by: root <root@e00e7b323342>

version-0.26.0

Toggle version-0.26.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(kotlin): move to new kotlin version and upgrade kork (spinnaker…

…#981)

version-0.25.1

Toggle version-0.25.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(gcs): Fix startup error when bucketLocation is not specified (spi…

…nnaker#934) (spinnaker#938)

* test(gcs): Add some implementations to FakeStorageRpc

In an upcoming commit, we'll need to also support getting a bucket;
to prepare for that let's update the FakeStorageRpc to:
* Keep track of what bucket objects are in (rather than now where it
assumes they are all in the same bucket)
* Handle creating and getting a bucket

We'll add an additional Map around the blobs data structure that
maps the bucket to a Map of blobs.  (This is a bit of a complex
data structure that in production code might be better expressed
as classes, but for this single fake in a test it's porbably fine.)

Creating a bucket initializes its blobs to an empty map; we know
if a bucket exists by whether it has an entry in the map.

I used the documentation on the interface we're mocking to decide
how to handle a missing bucket; in some cases we just return null
(when getting an object or a bucket) while in others we propagate
the 404.

This required one small change to the existing tests, which is that
we'll need to create the bucket before we use them in the tests.

* test(gcs): Add test to demonstrate NPE on missing bucketLocation

This commit adds a broken test to demostrate the NPE that occurs
on startup when the bucketLocation is not specified.

* fix(gcs): Fix startup error when bucketLocation is not specified

There was a regression in 1.22 where omitting bucketLocation from
one's GCS config now causes an error on startup. Prior to the
rewrite of GcsStorageService, we accepted either null or empty
string as the bucket location; now that GcsStorageService is in
kotlin and does not use a String? for the field, an error occurs
on trying to create the GcsStorageService.

The fix is just to default the string to "" in the config properties.

* style(gcs): Use Bucket.of intead of builder

* test(gcs): Replace nested map with classes

To simplify the nested map, define a Buckets class and a
BucketContents class, with operation names that make it more
clear what is happening.

Also, I realized that before my changes we were appending the bucket
name to the object name before putting it into the map, but now we
don't need to do that anymore because we have a separate map for
each bucket, so remove some unecessary calls to fullPath (which is
now only used in printing error messages).

* style(gcs): Fix typo

* style(gcs): Fix constructor

There's no need to accept the map in a private constructor then
separately define a no-arg constructor that passes an empty map,
just make the map a val in the class.

(cherry picked from commit ba4b061)

Co-authored-by: Eric Zimanyi <ezimanyi@google.com>

version-0.25.0

Toggle version-0.25.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
chore(dependencies): Autobump spinnakerGradleVersion (spinnaker#926)

Co-authored-by: root <root@6a807b439d68>

version-0.24.1

Toggle version-0.24.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
fix(provider/Oracle): Cache issue related to Oracle Object Storage (bp 

…spinnaker#886) (spinnaker#923)

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: CyrusKOCI <66336602+CyrusKOCI@users.noreply.github.com>
0