Closed revelt closed 6 years ago
Hey,
greenkeeper-lockfile only runs on branches created by greenkeeper (the ones called: greenkeeper/dependency-xyz
) therefore it is correct that it does not run on master
.
For the GH_TOKEN
: it is needed for every repository. Without the token greenkeeper can not create a commit and push it to the branch (to update the lockfile).
You can add Enviroment Variables to a CI setup in the settings of your CI. They are then automatically available during the build process.
Here is what the settings page for Travis CI looks like:
looking at this branch build: https://travis-ci.org/codsen/string-remove-duplicate-heads-tails/builds/331317448 it seems you were successful in setting it up.
I'll look into adding some example travis.yaml files and explainations in the readme.
Thanks!
hi all,
I try to enable
greenkeeper-lockfile
on Travis-ci.org, on an open source package, string-remove-duplicate-heads-tails.I tried the provided snippet for Travis,
it does not work. Each commit I publish consists of two commits actually, "master" and another that is incurred by
npm version ...
. I thought, maybe isolating "master"-only would help. Apparently, not. See the last line "except" I nicked from this package's.travis.yml
:I tried specifying latest Node and targeting different Node versions, no luck.
I thought maybe I need to provide
GH_TOKEN
explicitly for this package. I generated the token, ran the Travis CLItravis encrypt GH_TOKEN=<token> --add
, it added bunch of encrypted characters onto my.travis.yml
, but that didn't work either. Looks like it didn't recognise Node project and ranrake
. Apparently,language: node_js
row is obligatory...I tried other variations of
.travis.yml
and none worked, often causing whole Travis build to fail.The documentation of this package is either incomplete or dare I say, also erroneous. Besides Travis snippets in this documentation that don't work out-of-the-box, I want to make some observations:
.travis.yml
?Your implementation is not standard since it is not using your supplied snippets. Technically speaking, you're cheating - your
.travis.yml
links to JS files with a fancy custom setup. What we need is a link to a normal open source library which usestravis-ci.org
and which used your setup instructions verbatim and where Greenkeeper updated its lockfiles.Dear maintainers, I challenge you to find at least one open source library uses your supplied Travis snippets and link to it.
Personally, I find this tool impossible to set up. It took me all Saturday morning and within 8 attempts/tweaks/releases I could not get string-remove-duplicate-heads-tails Greenkeeper to update lockfiles. Greenkeeper itself, on other hand, activated automatically.
Dear maintainers, do you see my frustration here?
On the positive side, thank you for all this anyway; some tooling is better than no tooling and hopefully we can automate lockfile updates eventually. That would save lots of time maintaining OS libraries. 👍