The release-manager's discuss from snowdrop

Paralellize tasks

There are lots of opportunities to run things in parallel (in particular, all ticket creations / linking).

Generate report from JIRA tickets information

Output link to operated on issue instead of just its key

Error compiling project due to missing project 3.1.7

When building the project using mvn clean package it fails with the following error:

[ERROR]   The project me.snowdrop:jira-tool:1.0-SNAPSHOT (/z/dev/client/redhat-snowdrop/jira-tool/pom.xml) has 3 errors
[ERROR]     Non-resolvable import POM: Could not find artifact com.atlassian.platform:platform:pom:3.1.7 in atlassian.com (http://maven.atlassian.com/public/) @ com.atlassian.jira:jira-rest-java-client-parent:5.0.4

This is due to version of the com.atlassian.jira:jira-rest-java-client-parent:5.0.4 which depends on...

<dependency>
<groupId>com.atlassian.platform</groupId>
<artifactId>platform</artifactId>
<version>3.1.7</version>
<type>pom</type>
<scope>import</scope>
</dependency>

...and the dependency is missing.

Update release.yml with the keys of all linked tickets when using start-release

This command would encapsulate both the clone and create component commands in one command to avoid having to perform these actions separately and have the potential of error when passing the cloned issue.

Refactor and update Readme

The table of contents is not up to date.
The link to the release.yml example file is wrong

Compilation of the project is failing

Issue

mvn clean package
...
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ issues-manager ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 6 source files to /Users/cmoullia/code/snowdrop/issues-manager/target/test-classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] error reading /Users/cmoullia/.m2/repository/io/quarkus/quarkus-bootstrap-app-model/1.8.1.Final/quarkus-bootstrap-app-model-1.8.1.Final.jar; zip file is empty
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/MockProjectRestClient.java:[14,1] cannot access dev.snowdrop.jira.atlassian.model
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/JodaDateTimeTest.java:[1,1] cannot access dev.snowdrop.jira
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/MockJiraRestClient.java:[40,8] cannot access dev.snowdrop.jira.atlassian
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/Utility.java:[6,8] cannot access dev.snowdrop
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/MockPromise.java:[27,8] cannot access dev
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[16,8] cannot access java
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[20,8] cannot access javax
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[20,13] cannot access javax.inject
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[22,8] cannot access io
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[22,10] cannot access io.quarkus
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[23,8] cannot access org
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[23,11] cannot access org.junit
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[25,24] cannot access org.junit.jupiter
  zip END header not found
[ERROR] /Users/cmoullia/code/snowdrop/issues-manager/src/test/java/dev/snowdrop/jira/atlassian/model/ReleaseTest.java:[26,32] cannot access org.junit.jupiter.api
  zip END header not found
[INFO] 15 errors 
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  56.074 s
[INFO] Finished at: 2020-09-28T17:15:20+02:00
[INFO] ------------------------------------------------------------------------

Error authenticating with Jira

Of course, the code will fail now as we don't yet use OAuth

Caused by: RestClientException{statusCode=Optional.of(401), errorCollections=[]}
        at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:178)
        at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:170)
        at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:67)
        at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:11)
        at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:295)
        at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:185)
        at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
...
 <div class="aui-message aui-message-warning warning">
                            <p>Encountered a <code>&quot;401 - Unauthorized&quot;</code> error while loading this page.</p>
                            <p>Basic Authentication Failure - Reason : AUTHENTICATED_FAILED</p>
                            <p><a href="/secure/MyJiraHome.jspa">Go to Jira home</a></p>
                        </div>

Cloning from an issue should add a link to the cloned issue for reference purpose

Create template for "indirect" product request

This will be the text used for JIRA tickets created for information request for teams supporting products we bundle in our starters.

Generate product requests with fill-in information in the description

This way, it should be easier for product teams to provide us the information we need in a format that we should be able to process automatically.

Review code

Improve product ticket title

Right now, it's using the same title as the associated project which is confusing.

Default "Dependency" link type is not available anymore

This results in failure to link CVE issues to the master release ticket. Not sure why the link type doesn't exist anymore, though… :thinking:

Add test flag to `start-release` command

… so that we can test the product requests without spamming their respective projects by using the SB project instead.

Rename project to issues-manager

The name is more generic. What do you think, @cmoulliard?

Separate CVE handling from cloning operation

Since this has nothing to do with a pure cloning operation.

Link relation direction is incorrect

Product tickets are marked as being "blocked by" the master release ticket when it should be the contrary.

Simplify CVEs by using Issue instead of specific object

Continue quarkification

Initial work has been done but using CDI is proving not trivial and the app doesn't work with it at the moment.

Populate a github issue ticket with status update about a release or CVE

Feature request

Populate a github issue ticket where the description of the ticket will contain a status report about a release like also for the the CVE

The description will contain 2 tables where one is about the releases and the second about CVE

The release table will include for each release the list of the linked and related tasks, their status and if some tasks are still older than 1month and where status is still new, work in process, then a small red box will be displayed in front of the line to warn the team and product owner

The CVE will be similar as the release table but will also include the labels able to decorate, enhance the description of the progress did around the issue

Java JIRA create error : fixVersions=Field 'fixVersions' cannot be set. It is not on the appropriate screen

Issue

When we try to create an issue where se set the fix version

 java -jar target/uber-atlassian-1.0-SNAPSHOT.jar \
    -user 'yyyyyy' \
    -password 'xxxxxxx' \
    -cfg etc/release.yaml \
    -action create \
    -url https://issues.redhat.com

then we got this error

Exception in thread "main" RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={fixVersions=Field 'fixVersions' cannot be set. It is not on the appropriate screen, or unknown.}, errorMessages=[]}]}
        at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:45)
        at dev.snowdrop.jira.atlassian.Client.createIssue(Client.java:91)
        at dev.snowdrop.jira.atlassian.Client.main(Client.java:39)
Caused by: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={fixVersions=Field 'fixVersions' cannot be set. It is not on the appropriate screen, or unknown.}, errorMessages=[]}]}
        at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:176)
        at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:170)
        at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:49)
        at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:10)
        at io.atlassian.util.concurrent.Promises$OfStage.lambda$fold$4(Promises.java:332)
        at io.atlassian.util.concurrent.Promises.lambda$biFunction$7(Promises.java:422)
        at java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)
        at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)
        at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
        at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
        at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1.lambda$doCompleted$0(SettableFuturePromiseHttpPromiseAsyncClient.java:37)
        at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:61)
        at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:129)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

Problem

The error seems not related at all to a technical issue but is probably due to a lack of permissions as documented here

The fix was to ask my company's Jira administrator to allow all users to be able to set assignees and fixVersions when they create new issues.

Retrieve all JIRA tickets associated with a given release and extract product information from them

Generate release status based on linked JIRA tickets

When a release is created, the associated release.yml file should be updated with the created ticket so that we can then generate a status report for the release based on the information provided in the linked tickets.

Update request template

Based on work done in #8

Extract artifacts for a given product based on BOM

Assign component tickets to the stakeholder/leader

In order to notify the stakeholders responsible of filling in the information we need to assign the ticket to the right person. It could be nice if this task can be done automatically.
The leaders can be found here

Move master branch to archived and promote clean-up branch to master

… once #11 is finished.

Add explicit version to release

validate that it matches the associated parent version in the POM
validate that it matches the spring-boot.version in the POM

Investigate using a generic / bot account to trigger issues-manager

The account should be set up in such a way that it has appropriate permissions on jira and so that all engineering members of the team could get notified of answers to create jira tickets.

Validate issue type associated to each component when validating a Release

Create a continuous integration job

Adapt PR #32 to new architecture

Make it possible to customize the issue type to use for each component

This is needed because not all components support the default issue task type (looking at you EAPSUP! 👀)

Extract CVEs from JIRA instead of having to re-declare them in release.yml

Migrate to picocli

The goal being to simplify the command code and eventually move to quarkus.

Load pom and release information in parallel

Add name to component instead of inferring it from properties

Provide default issue to clone from if none is provided

By default, we should always clone from the same issue so this should be the default one unless we specifically override it.

Make it possible for a component request to create several tickets

The use case here is when we have a component that we support ourselves, we need to:

create a component request to release the starter
create a related product information request to get the product version our starter should target

README is not up to date anymore

Issue

The README is not up to date anymore as by example it does not document how to create a Component JIRA issue and link it to a JIRA Parent issue

Example of command not documented

java -jar ./target/uber-issues-manager-1.0.0-SNAPSHOT.jar \
    -user <user> -password <password> \
    -action create-component \
    -git "metacosm/spring-boot-bom/release-integration"

Question: Will it be needed to execute this command for each JIRA issue to be created for a component ? @metacosm

Improve CVE report with JIRA information

Add the hyperlink of the ENTSBT ticket link to a CVE/Bugzilla
Using the link provided in the report (or list of JIRA/Bugzilla records) to add the status, snowdrop release
Enhance the code to support OAuth

Update release.yml with the key of the created ticket if none was specified when using start-release

Add possibility to skip product tickets creation

This would allow to more easily reuse release definition from previous releases without having to remove the components definition in case we want to create a master release ticket without asking product teams for compatible versions (e.g. in case of minor or CVE-only release).

CI doesn't work

Clean-up code

Remove exploratory projects to only keep atlassian-prod
Rename project to issues-manager to be more generic

snowdrop / release-manager Goto Github PK

release-manager's Issues

Issue

Feature request

Issue

Problem

Issue

Recommend Projects

Recommend Topics

Recommend Org