Build properties seem incorrect
See original GitHub issueDescribe the bug
For staging, build properties in dockstore-deploy.properties
are
UiVersion=2.7-fa4b99a
ComposeSetupVersion=1.10
WebserviceTag=1.10.0
DockstoreLambdaKey=0.1.4-cac4598/upsertGitHubTag/function.zip
StackName=Dockstore-1-10-0
but the UI reports
Webservice - 1.10.0 UI - 2.7 Compose Setup - 1.1 Deploy - 1.1
in the footer
┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.10.X ┆Issue Number: DOCK-1662 ┆Sprint: Sprint 52- Angel shark ┆Issue Type: Story
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
RE: Incorrect path to Tomcat in build.properties? - Forums
Trying to execute one Ant target I found an error, which led me to build.properties file. My file contains the following lines at...
Read more >32 - Stack Overflow
properties but it does not solve my problem. It seems to me that gradle is NOT reading my ~/.gradle/gradle.properties file. I have a...
Read more >Solving common problems - Gradle User Manual
Other issues with the build won't cause it to produce incorrect results, but will lead to unnecessary cache ... You can do so...
Read more >58648 – ARPlaneAnchor.Extent property seems incorrect but ...
In ARKit, the system generates `ARPlaneAnchor` objects whose `Extent` property holds the size (in floating point meters) of the detected plane.
Read more >TeamCity build.vcs.number seems to be incorrect – TeamCity ...
build.vcs.number% seems to be incorrect for some jobs which we are running. ... allowCaching=true in the internal.properties file on the TC server.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, pretty sure that’s it – I think I meant to comment on this but forgot to. At any rate, I believe if you put these values in double quotes it would fix it: https://github.com/dockstore/compose_setup/blob/47a7d7fcf8e64e86d33fb09a821ce00a35fc5254/templates/web.yml.template#L185
Closing bc verification is not easily do-able and the code was reviewed.