You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A pipeline context is the conditions in which a job was built or triggered. For example,
Triggers:
Manual trigger
Cron trigger
PR comment trigger
Push trigger
Environment context based on Git workflow:
Pull request
Branch
Tag
Conditional disabling "Build Project"
Also, Matrix building of "Build Project" should be conditional
Support for disabling matrix building based on pipeline context. isBuilding() pipeline step should be internalized into Jervis so that it can be used for filtering. It should be extended so that PR comments are also supported.
build:
on:
- pr
- tagmatrix:
on:
pr_comment: '/.*[Bb]uild +[Pp](ull +)?[Rr](equest)? +[Mm]atrix.*/'
The filtering should be context aware and Jervis should be instantiated by loading in the context of the pipeline in which it is building.
Support for disabling building
Add support for
build:
on: 'never'jenkins:
pipeline_jenkinsfile: '.ci/Jenkinsfile'
The following would also produce not ever building.
Because it is possible a user only wishes to use Jervis for toolchains and any building would happen in their Jenkinsfile.
A user overriding the install and script for a language to execute the documented no-op build means they only want the toolchains for that given language. to
The text was updated successfully, but these errors were encountered:
Tasks
Defining pipeline context
A pipeline context is the conditions in which a job was built or triggered. For example,
Triggers:
Environment context based on Git workflow:
Conditional disabling "Build Project"
Also, Matrix building of "Build Project" should be conditional
Support for disabling matrix building based on pipeline context.
isBuilding()
pipeline step should be internalized into Jervis so that it can be used for filtering. It should be extended so that PR comments are also supported.The filtering should be context aware and Jervis should be instantiated by loading in the context of the pipeline in which it is building.
Support for disabling building
Add support for
The following would also produce not ever building.
Because it is possible a user only wishes to use Jervis for toolchains and any building would happen in their Jenkinsfile.
A user overriding the install and script for a language to execute the documented no-op build means they only want the toolchains for that given language. to
The text was updated successfully, but these errors were encountered: