Details
-
Type: New Feature
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.25
-
Epic Link:
-
Sprint:Fall 4 : 30 Sep to 11 Oct
Description
The branch pipelines for IGB project start with a wget command to retrieve assets from a private repository. This fails if the person (fork) running the pipeline does not have read access to this private repository.
Currently, the wget command is using username and password flags, which get replaced by repository environment variables configured by the developer.
It would be simpler and easier if we could use the BB_AUTH_STRING instead, because the user name in question would be encoded there. If we can do that, then developers will not have to enter the username and password.
Attachments
Issue Links
- relates to
-
IGBF-2047 Improve IGB CR pipeline
- Closed
Activity
Ann Loraine
created issue -
Ann Loraine
made changes -
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1531 [ 17617 ] |
Ann Loraine
made changes -
Ann Loraine
made changes -
Rank | Ranked higher |
Ann Loraine
made changes -
Status | Open [ 1 ] | To-Do [ 10305 ] |
Ann Loraine
made changes -
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Ann Loraine
made changes -
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Ann Loraine
made changes -
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Ann Loraine
made changes -
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Ann Loraine
made changes -
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Ann Loraine
made changes -
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Ann Loraine
made changes -
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Ann Loraine
made changes -
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Ann Loraine
made changes -
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Ann Loraine
made changes -
Workflow | Fall 2019 Workflow Update [ 20805 ] | Revised Fall 2019 Workflow Update [ 22532 ] |
Findings:
In addition:
The way this works is very simple. This is a feature of maven. If your plugin needs a property defined in the pom.xml as a special tag (e.g., "special.tag"), you can set its content to be $
{some_variable}. Then, you pass in the value of the variable as an option to maven, like this:
You can either pass in the literal value or use an environment variable named "some_variable".
I'm not sure if this works for every possible property/tag. I bet it does, though. I would like to look into it a bit more.
Also, I learned that our install4j configuration file indicated that the location of our jar-signing files was in "/opt/igb", which did not actually exist in our Docker image.
If you don't specify an absolute path, Install4J looks for the indicated key files in "distribution" in the IGB project.
I made changes to pom.xml, bitbucket_pipelines YML, and install4j configuration files to take advantage of above features of maven and pipelines. Changes are merged now into master.
Also, I modified how the pipelines run so that the default pipeline does not try to build installers. This is so that developers that are not building and releasing IGB can still build the project using pipelines. If they do that, what will happen is that an executable jar file containing the IGB version and their bitbucket user name will get build and copied into their fork's download section.