-
Suggestion
-
Resolution: Won't Fix
Reproducible builds are gaining popularity recently. One option on way to deterministic builds is to use the last modification time of the source as a current time during build. SOURCE_DATE_EPOCH environment variable is a standard proposed by Debian team to achieve the goal.
Right now we need to do something like this:
Unable to find source-code formatter for language: shell. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
export SOURCE_DATE_EPOCH=$(git show -s --format=format:%ct HEAD)
somewhere inside of build script for each step. Which is not so convenient since there is no variable sharing between the steps, hence forces you to use copy/paste pattern in your code.
All needed info (commit timestamp) should be already available at the time pipeline starts, so it should be trivial enough to export as environment variable.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!