-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI jobs for readable-stream group #782
Comments
cc/ @piccoloaiutante @nodejs/streams |
excellent, go ahead 👍 |
+1 |
@gibfahn let me know if you need any help on this |
Created the streams-admins team and added @mcollina and @calvinmetcalf (and made both maintainers). I don't know enough about the WG to know who else will be active in maintaining Jenkins jobs. If anyone else should be added comment in this thread. |
Gave the two teams the appropriate access to readable-stream-continuous-integration, @mcollina please confirm you still have configure access. |
It is all working. I removed some unneeded machines and the ones that suffer from #785. Some things that I would like fixed:
Overall it works very well, I had to fix a configuration on our side. If you want to test, use the |
Looks like @nodejs/streams didn't have build access (@nodejs/streams-admins did have edit access) because it's actually
What I've been doing for other projects is adding a pipeline that runs the job with a list of versions, current job is here: https://ci.nodejs.org/view/All/job/readable-stream-pipeline/. It doesn't do anything magical, it just splits the |
BTW, if you want to add or remove platforms you modify the |
How can we have some form of aggregated test results for each platform and some reporting for the pipeline? My jenkins fu is extremely bad and out-of-date :(. |
Sorry, I should have mentioned that I'm still working through your other requests! |
thanks @gibfahn! |
Closing due to long period of inactivity. Feel free to re-open if this is a thing. I'm just trying to close stuff that has been ignored for sufficiently long that it seems likely it's not something we're going to get to. |
Setting up initial jobs for readable-stream WG in #657
I'll create a
streams-admins
group following our process. That group will have edit access,streams
will have run access.@nodejs/build let me know if there are any objections.
The text was updated successfully, but these errors were encountered: