-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Tolerate changelist.format=%d.v%s #14
Conversation
so /shrug |
Indeed CI seems to be off. Running |
Oh I see what you mean, that does not run tests. In abcdf72 you did not update I tried to diff --git a/Dockerfile b/Dockerfile
index ef074ec..fab5076 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -17,4 +17,6 @@ RUN npm install
# Bundle app source
COPY . .
+RUN npm test
+
CMD [ "node", "index.js" ] but this complains something about Mocha. |
yea the docker file only runs npm install with NODE_ENV=production I would say don't worry about it, if i get a min I'll make a multi stage docker image that runs tests first |
Anyway, do you own this service? I apparently have write permissions to the repo but I should not be merging PRs. |
i assume this needs a version bump and a tag for release @halkeye ? |
yea, its the standard docker ci system, so bump version and generate tag and ci will take care of the rest |
@halkeye @timja you know this is still not live, right? https://ci.jenkins.io/job/Core/job/jenkins-test-harness/job/PR-280/10/execution/node/32/log/ |
updateCli was disabled for some reason, seems fixed now, PR is up at jenkins-infra/kubernetes-management#923 |
Noticed in jenkinsci/jenkins-test-harness#277 that incremental deployment was not working, due to jenkinsci/incrementals-tools#19 breaking the assumption about the final version format. Amends #10 which was introduced for the previously recommended JEP-229 format.