CI Env Abstraction

[finite beacon]

Can you give me some examples of the type of variables you have in mind?

[odd grail]

https://docs.gitlab.com/ee/ci/variables/predefined_variables.html

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables

https://www.jenkins.io/doc/book/pipeline/jenkinsfile/#using-environment-variables

All those variables encompass different paradigm for a CI lauch job to know about itself

I think it would be helpful to have consistency

if I'm migrating between different CI provider I want to have as much consistency as possible, dagger could help with that by ensuring that if I want to have the hash of my commit for instance I have a consistant way of accessing it. Plus having a map about the different translations of the same concepts from one CI provider to the next could help for people that are migrating

[finite beacon]

Thanks for the details! Totally makes sense. There are no plans to do this right now, but I can totally see the benefit.

Would you be open to making a GH issue for this? That is likely a better place to continue the discussion https://github.com/dagger/dagger