Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip build in bash if azure isn't playing along #511

Merged
merged 1 commit into from
Feb 28, 2020

Conversation

hardbyte
Copy link
Collaborator

@hardbyte hardbyte commented Feb 20, 2020

The condition in azure didn't seem to take effect so we now check whether to skip the expensive image building in bash. I've tried various combinations of using strings and booleans in the main azure script and docker build template and cannot make Azure Pipelines do what I expect.

I updated the base digest too

Copy link
Collaborator

@wilko77 wilko77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if we change the skip to a Boolean. Then, the condition would become not(${{ parameters.skip }}) and the default default: false. No need for the extra bash script checking stuff.

@@ -88,7 +88,7 @@ stages:
dependsOn: HashBaseDependencies
imageName: data61/anonlink-app
# this part is still todo automated
dockerBuildArgs: "--build-arg VERSION=02a973ce02c96d24376c5770c0426ccb0958a0d59136a4f2fc11c8666c43062a"
dockerBuildArgs: "--build-arg VERSION=ed0be6ee130ec505b2a65af26ba570e1033ffb7e0cc6b27b6a8520df94f65d20"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is really annoying. When we change the base image requirements, although a new version gets build, it will not be tested. We already had a non-functioning base image. We really need to find a way to test the new base images straight away.

@wilko77 wilko77 self-requested a review February 28, 2020 04:58
Copy link
Collaborator

@wilko77 wilko77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, that was a bit of a premature recommendation, as I can't make that work within our context.
I guess we just merge this in for now until someone with magic Azure-pipeline-superpowers comes along and guides us out of this misery...

@hardbyte hardbyte merged commit febb2a7 into feature-blocking Feb 28, 2020
@hardbyte hardbyte deleted the bugfix-azure-base-build branch February 28, 2020 06:49
@hardbyte
Copy link
Collaborator Author

Agree it could be nicer if Azure was a bit easier to use.

Have added the need to automate using and testing the latest base image to the backlog.

@hardbyte hardbyte restored the bugfix-azure-base-build branch February 28, 2020 06:53
@hardbyte
Copy link
Collaborator Author

Oh that is annoying, I set the merge target as feature-blocking. Will recreate...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants