fix: Tuleap job should send the right SHA-1 to the Tuleap git repository #353
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
request #21765 Tuleap PR autonotification notify the git repository with a inexistent SHA-1 For each checkouted git repository by Jenkins a new Git Build Data is created. The current implementation does not take in account that case, the consequence is when there are more than one Git Build Data, we may notify the Tuleap git repository with an invalid SHA-1. To test, you can use a shared library and add it in your Jenkinsfile For example, you can use: https://github.com/monodot/pipeline-library-demo as shared library => The right Tuleap repository with the right SHA-1 should be notified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
request #21765 Tuleap PR autonotification notify the git repository with a inexistent SHA-1
For each checkouted git repository by Jenkins a new Git Build Data is
created. The current implementation does not take in account that
case, the consequence is when there are more than one Git Build Data,
we may notify the Tuleap git repository with an invalid SHA-1.
To test, you can use a shared library and add it in your Jenkinsfile
For example, you can use: https://github.com/monodot/pipeline-library-demo as shared library
=> The right Tuleap repository with the right SHA-1 should be notified