Closed xgalen closed 7 years ago
This is possibly an issue we recently found with a silent failure in the simple runner, related to caching,. Try clearing the cache for the project. All the debug messages that are not prefixed with strider
are usually not relevant to diagnose issues.
There is an option for that in the project settings.
After clearing the project's cache works worse. No phase is shown, the black window remains fully black.
Now I got this errors:
2016-08-05T07:52:33.770Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent max redirects 5
2016-08-05T07:52:33.770Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent set User-Agent "StriderCD (http://stridercd.com)"
2016-08-05T07:52:33.771Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent query ref=master
2016-08-05T07:52:33.771Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent set Authorization "token 3f40a75fd7a2903c69d0150100b551ef063a6d0f"
2016-08-05T07:52:33.771Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent GET https://api.github.com/repos/mediasmart/MYREPO/contents/strider.json
2016-08-05T07:52:33.815Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent GET https://api.github.com/repos/mediasmart/MYREPO/contents/strider.json -> 404
2016-08-05T07:52:33.816Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent end GET https://api.github.com/repos/mediasmart/MYREPO/contents/strider.json
2016-08-05T07:52:33.817Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent clear timeout GET https://api.github.com/repos/mediasmart/MYREPO/contents/strider.json
Fri, 05 Aug 2016 07:52:33 GMT strider:backchannel job.prepare - strider.json not found, skipping config merge
2016-08-05T07:52:33.844Z - error: Fri, 05 Aug 2016 07:52:33 GMT superagent clear timeout GET https://api.github.com/repos/mediasmart/MYREPO/contents/strider.json
We do not use strider.json
but I see also is looking for into a folder of my repo ¿?.
Yes, it's always looking for that file. Issues like this are really annoying. Strider doesn't log nearly as much as it should to make analyzing these issues possible :P
Finally the environment
phase has appeared, like before, but not more.
Sadly, @knownasilya is on vacation and I'm leaving for the weekend soon as well. The only suggestion I have left at this point is to try to run the absolutely latest development snapshots of everything. The clone
and link
scripts in https://github.com/oliversalzburg/strider-dev can be very helpful for that.
Sorry :(
Enjoy it @knownasilya !! Ok @oliversalzburg , enjoy your weekend too. I gonna try this, put the feedback and if does not work I will downgrade Strider until it works and continue the next week.
I can only offer a "this works for me" for the time being: We use Docker to run our tests and configure mainly through strider.json
. The process is outlined at https://github.com/Strider-CD/strider/wiki/Advanced-Configuration
The Docker runner differs in many ways from the simple runner you're currently using. So it's different code (that has different problems). But maybe that approach works better for you ;)
Finally I got Strider working with simple-runner. What I did:
git clone .. && npm install
simple-runner
(1.0.0 to 1.0.1) and custom-scripts
(0.x.x to 1.0.0) plugin in the plugins page. I've also updated email-notifier
but I don't think that has effect.I think Strider should installs the latest version of the plugins by default. I let the issue open with this suggestion and you can close if don't like it.
Anyway, I will let a chance to docker-runner
coming soon. Thanks!
I bumped the versions of the two mentioned plugins.
Thanks again.
@oliversalzburg when installing strider in a new machine I'm having an error, I think related with this. Running npm install
:
npm ERR! notarget No compatible version found: strider-simple-runner@'>=1.0.1 <2.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.10.0","0.11.0","0.11.1","0.11.2","0.11.3","0.12.0","0.12.1","0.13.0","0.13.1","0.14.0","0.15.0","0.15.1","0.15.2","1.0.0"]
The point is before the strider's package json the simple-runner had ^1.0.0 so it had to install the 1.0.1 but didn't. On the other hand, when I updated through the UI it worked.
The same problem with strider-custom
, in this case de semver does not match though:
npm ERR! notarget No compatible version found: strider-custom@'>=1.0.0 <2.0.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.1.0","0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.3.0","0.3.1","0.4.0","0.4.1","0.5.0","0.5.1","0.5.2","0.5.3","0.5.4","0.5.5","0.6.0","0.6.1"]
The two plugins are currently only published to the "ecosystem index" (making them available as updates through the UI). The release to npm is still pending (I don't have npm publish access). I reverted the commit for now.
I think we can close this. No problems anymore after upgranding Strider and node.
Hi,
After upgrading to the Strider's latest, the jobs (manual retest) don't finish the
environment
phase and don't do nothing else.Node v4.4.7.
Using
DEBUG=*
I see this:And latest lines are repeated after some seconds but the job never ends.
The weird character "�3" appears sometimes in the log.