Comments (5)
Hello,
it is not clear what you are asking. Could you please clarify and make a complete example?
from cogito.
Sure! Our staging environment is a complete mirror of production, meaning the pipelines there make extensive use of your pr resource. With 2 or 3 jobs per pipeline that manage PRs and 4 times per job that cogito is called (once prior to performing an activity, once on failure, once on success, and once on error) the act of disabling cogito notifications in the staging environment prior to working on a new feature could involve as many as 10 blocks of yml to disable or delete in order to not see notifications be pushed back to the PR branches in question.
THe feature I was thinking of is way to tell the resource where cogito is configured to suppress notifications, meaning we could leave the job yml untouched and enable "Dry run" or similar on the resource to suppress notifications in lower environments.
Make sense now or do you need me to explain in a different way?
from cogito.
You mean that you would have two pipelines, almost identical, one for prod and one for staging.
The staging one would, say, set dry-run: true
in the source
settings of Cogito?
Actually that line should be there always, and prod would set dry-run: false
.
This could be done via a ((var))
:
dry-run: ((dry-run))
and then
fly set-pipeline ... -y dry-run=false <- prod
fly set-pipeline ... -y dry-run=true <- staging
Is this what you mean?
I have to think.
from cogito.
@eitah ping
from cogito.
Thanks for following up on this. Yea, you understood the feature request, a source configuration for the resource such that the status is not actually published anywhere for our staging environment without necessitating a lot of conditionals in the YML.
from cogito.
Related Issues (15)
- Support custom user configuration in integration tests HOT 1
- When retrying an HTTP request to GitHub, Cogito does not print why
- cogito: error: put: internal error: unexpected: negative sleep time: 0s HOT 1
- report commit author and message
- retry GitHub HTTP request when rate limited: does not sleep when it should
- What json data should be passed onto STDIN when testing /opt/resource/out? HOT 2
- Build links for instanced pipelines don't work HOT 8
- Support GH App Installation Access HOT 4
- Support repos cloned via ssh HOT 4
- Provide a way to override BUILD_JOB_NAME === context on resources. HOT 10
- Add pipeline name as prefix to context HOT 5
- Support for Instanced Pipelines in Details Link HOT 2
- Feature request: configurable description HOT 3
- Support for Enterprise Github? HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cogito.