Support the "environment" field in the Pipeline and Job webhook events #1297
Conversation
This file contains hidden or 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
lucasls
force-pushed
the
feature/webhook-environment-field
branch
from
551c1c3 to
306a159
Compare
lucasls
changed the title
lucasls
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Pipeline and Job webhook events support the
environmentfor deployment jobs, but they are missing in the library.You can find more information at https://docs.gitlab.com/user/project/integrations/webhook_events/ (search for
"environment": {to see an example).I noticed the
Buildclass is not in themodelspackage, instead ofwebhook. I didn't change it since it'd break compatibility, but let me know if you think I should change something about it.