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.

Sign up for GitHub

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

Jump to bottom

Build artifact checksum not working #3007

Closed
squakez opened this issue Feb 11, 2022 · 0 comments · Fixed by #3008
Closed

Build artifact checksum not working #3007

squakez opened this issue Feb 11, 2022 · 0 comments · Fixed by #3008
Assignees
@squakez
Labels
kind/bug Something isn't working
Milestone
1.8.1

Comments

@squakez
Copy link
Contributor

squakez commented Feb 11, 2022

In version 1.8.0 it seems we are having some problem calculating the artifact checksum:

    - checksum: 'sha1:'
      id: org.apache.camel.k.camel-k-core-support-1.11.0.jar
      location: /tmp/kit-c833h1hc11s3mviqhgcg-700756872/maven/target/quarkus-app/lib/main/org.apache.camel.k.camel-k-core-support-1.11.0.jar
      target: dependencies/lib/main/org.apache.camel.k.camel-k-core-support-1.11.0.jar
    - checksum: 'sha1:'

We always have an empty value. This behavior may affect the incremental build, resulting every IntegrationKit built from base image (so, no incremental image available at the moment).
@squakez squakez added the kind/bug Something isn't working label Feb 11, 2022
@squakez squakez added this to the 1.8.1 milestone Feb 11, 2022
@squakez squakez self-assigned this Feb 11, 2022
This was referenced Feb 11, 2022
Closed
Closed
squakez added a commit to squakez/camel-k that referenced this issue Feb 11, 2022
@squakez
fix(build): incremental build
799c691 
* Fixed the SHA1 which were not calculated properly
* Added a check to verify that the base image != default expected
* Unit and E2E test to make sure we'll be warned if the behavior is broken again

Closes apache#3007
@squakez squakez mentioned this issue Feb 11, 2022
Merged
squakez added a commit to squakez/camel-k that referenced this issue Feb 15, 2022
@squakez
fix(build): incremental build
d6513e2 
* Fixed the SHA1 which were not calculated properly
* Unit and E2E test to make sure we'll be warned if the behavior is broken again

Closes apache#3007
astefanutti pushed a commit that referenced this issue Feb 15, 2022
@squakez @astefanutti
fix(build): incremental build
bba4b5b 
* Fixed the SHA1 which were not calculated properly
* Unit and E2E test to make sure we'll be warned if the behavior is broken again

Closes #3007
squakez added a commit to squakez/camel-k that referenced this issue Feb 15, 2022
@squakez
fix(build): incremental build
88a7b14 
* Fixed the SHA1 which were not calculated properly
* Unit and E2E test to make sure we'll be warned if the behavior is broken again

Closes apache#3007
@squakez squakez mentioned this issue Feb 15, 2022
Merged
squakez added a commit that referenced this issue Feb 17, 2022
@squakez
fix(build): incremental build
d47fbad 
* Fixed the SHA1 which were not calculated properly
* Unit and E2E test to make sure we'll be warned if the behavior is broken again

Closes #3007
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@squakez squakez

Labels
kind/bug Something isn't working
Projects
None yet
Milestone
1.8.1
Development

Successfully merging a pull request may close this issue.

fix(build): incremental build squakez/camel-k
1 participant
@squakez