Actually it seems pretty straightforward.
Here is the things I have done:
Already have a project on Github
Create a project on Youtrack
Create "MD-Committers" group on Youtrack, give admin privileges on all projects.
Add myself to the group.
Create post-commit service hook for Youtrack with following options
.
url: http://myusername.myjetbrains.com/youtrack
committers: MB-Committers
username: root
password: ******
active: True
with these settings, I Test Hook button says Payload sent successfully which means, I presume, I have set it correctly.
Then,
Create an issue: MD-2 integration test
Commit and push to dev branch with comment: #MD-2 Fixed integration-test
At this point, I should be able to see the issue status set to Fixed and see the commit in the history. However, no status updates, no commits in the history.
My-email address on Youtrack and Github are the same, the only thing different is that, in commits, I use my full name rather than my nickname.
Here is the git log results:
commit 3e91ec7021b2a87a7e4b1b79e0f53e67707e8bf4
Author: Umur Kontacı <fastreload#gmail.com>
Date: Mon Jul 9 21:10:04 2012 +0300
#MB-2 Fixed integration-test
commit 48686795be37aa69ca2dd7b2cd176b57945dc229
Author: Umur Kontacı <fastreload#gmail.com>
Date: Mon Jul 9 21:05:14 2012 +0300
#MB-2 fixed integration-test
commit 8faa55c0589e3d0f91a9988fa5aa60126651ba69
Author: Umur Kontacı <fastreload#gmail.com>
Date: Mon Jul 9 21:04:11 2012 +0300
#MB-2 finished integration-test
commit 4b41acfd17fbeba6b220adaef7b0dd113130a037
Author: Umur Kontacı <fastreload#gmail.com>
Date: Mon Jul 9 20:55:13 2012 +0300
[Finished MB-2] integration-test
None of the commits has made to Youtrack.
What the heck I am missing here?
YouTrack parses GitHub comments as following form [some comment text] #issueID <command_1> [command_2] ...[command_n] as this link mentioned.
The rule of thumb is that, any comments should be placed before #issueID and acknowledgeable YouTrack commands should be placed after the #issueID.
So, integration-test may not be properly acknowledged in YouTrack, because integration-test is just handled as unknown YouTrack command.
Some comment #MD-2 Fixed should work, or #MD-2 Fixed tag integration-test may change your issue to Fixed status and integration-test tagging.
Example commands can be found at http://confluence.jetbrains.com/display/YTD5/Command+Grammar
Note 1: recommend you to see the walkthrough video http://www.youtube.com/watch?v=0iK1J_fWhns
Note 2: You may mistype MB-Committers in your post. probably MD?
Try to use your JetBrains account login instead of root.
Related
I have setup a job with Jenkins with MultiBranch pipeline.
Github is the SCM and is configured, with a webhook to fire a build on a PR commit. (Existing or new PR).
The build is triggered, all goes fine 1, however the CHANGE_ID is not set (null). We need the CHANGE_ID to pass on to Sonar.
I am struggling to understand, in which cases this parameter is set, and why it's null in our case.
Please consider this question from a Jenkins Multibranch perspective.
Our (git related) plugin installations is here [2] .
1 logging from Jenkins.
[Mon Jun 26 11:32:48 CEST 2017] Received Push event to branch BE-7394 in repository ServiceHouse/api UPDATED event from 172.18.0.1 ⇒ http://jenkins2.servicehouse.nl:8080/github-webhook/ with timestamp Mon Jun 26 11:32:43 CEST 2017
11:32:50 Connecting to https://api.github.com using shojenkinsuser/******
Looking up ServiceHouse/api
11:32:50 Connecting to https://api.github.com using shojenkinsuser/******
Looking up ServiceHouse/api
Getting remote branches...
Checking branch BE-7394
Getting remote branches...
Checking branch BE-7394
‘Jenkinsfile’ found
Met criteria
Changes detected: BE-7394 (01293286b6ee34056d8c92e21a6d39d18e537a81 → 35c16ef01bba5d27dd040a881cd3734fef271fd7)
Scheduled build for branch: BE-7394
0 branches were processed (query completed)
Done examining ServiceHouse/api
[2] Git related Installed plugins:
This variable sutup in the branch-api-plugin (setup source) and we have it working for pull requests or change requests.
For branches of the form -, it is not filled.
I can advise you to use:
BUILD_NUMBER
The current build number, such as "153"
BUILD_ID
The current build ID, identical to BUILD_NUMBER for builds created in
1.597+, but a YYYY-MM-DD_hh-mm-ss timestamp for older builds
I'm trying to build a project on Jenkins when a change is pushed to GitHub.
I'm using GitHub plugin and building on a slave node.
If the slave is online, everything works fine. However, if the slave is offline, Jenkins doesn't try to launch the slave node and ignores the notification from GitHub.
The following log is output to jenkins.log when the slave is online:
May 30, 2016 4:16:31 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent
INFO: Received POST for https://github.com/myname/myproject
May 30, 2016 4:16:31 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run
INFO: Poked MyProject
May 30, 2016 4:16:33 PM com.cloudbees.jenkins.GitHubPushTrigger$1 run
INFO: SCM changes detected in MyProject. Triggering #22
However, if the slave is offline, the build is not triggered:
May 30, 2016 4:15:58 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber onEvent
INFO: Received POST for https://github.com/myname/myproject
May 30, 2016 4:15:58 PM org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run
INFO: Poked MyProject
Starting a build by clicking "Build Now" always makes the slave node online. How can I build a project by GitHub changes on a slave node which might be offline?
Update:
I found the following message on "GitHub Hook Log" of the project:
Started on May 30, 2016 6:00:46 PM
We need to schedule a new build to get a workspace, but deferring 561ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
Done. Took 0.23 sec
No changes
Update(2016/06/01):
This is the current slave setting:
Contents of /var/lib/jenkins/bin/start-slave:
#!/bin/bash -eux
gcloud compute instances start ci-slave --zone us-central1-f
ssh ci-slave /var/lib/jenkins/bin/start
When I originally set up my Rules Engine service in Bluemix, I could deploy from my Eclipse Juno environment just fine. I just tried to deploy a new project this morning, and I got the following error in the deployment report in Eclipse:
ilog.rules.res.model.IlrAlreadyExistException: Unknown RuleApp: /RefillRulesApp/1.0. at
com.ibm.rules.res.internal.MutableRepositoryRESTAdapter.addRuleApp(MutableRepositoryRESTAdapter.java:86)
at
com.ibm.rules.decisionservice.internal.RESClient$3.execute(RESClient.java:332)
at
com.ibm.rules.decisionservice.internal.RESClient$3.execute(RESClient.java:1)
at
com.ibm.rules.decisionservice.internal.RESClient.safeInvokeRES(RESClient.java:132)
at
com.ibm.rules.decisionservice.internal.RESClient.deploy(RESClient.java:299)
at
com.ibm.rules.decisionservice.internal.DsResRestClient.deploy(DsResRestClient.java:168)
at
com.ibm.rules.studio.model.decisionservice.impl.Server.deploy(Server.java:310)
at
com.ibm.rules.decisionservice.DsRuleAppDeployManager.deploy(DsRuleAppDeployManager.java:38)
at
com.ibm.rules.decisionservice.DsDeployManager.deploy(DsDeployManager.java:88)
at
com.ibm.rules.studio.decisionservice.SDsXOMDeploymentJob.deploy(SDsXOMDeploymentJob.java:203)
at
com.ibm.rules.studio.decisionservice.SDsRuleAppDeploymentJob.deployRuleApp(SDsRuleAppDeploymentJob.java:101)
at
com.ibm.rules.studio.decisionservice.SDsRuleAppDeploymentJob.deploy(SDsRuleAppDeploymentJob.java:65)
at
com.ibm.rules.studio.decisionservice.SDsXOMDeploymentJob.runInWorkspace(SDsXOMDeploymentJob.java:81)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)**
I checked the RES console server log and there isn't any untoward messages in it
The Decision Server version infomation looks like this:
Version: Decision Server 8.7.0.1 , Decision Engine 1.10.0 Patch level: Build #2 on 2015-03-13 16:54:27 Release status: COMMERCIAL
Persistence Type: datasource (DB2/LINUXX8664 SQL10070) Startup
Time: Jan 29, 2016 4:17:18 PM GMT-05:00 Last Update Time: Feb 2, 2016
3:01:23 PM GMT-05:00
I checked for updates to the Eclipse plugin, and it looks like I am up to date.
If I check in the Explorer in the RES console, I can see that it partially deployed:
Deploy Picture
Notice how the rule app is greyed-out.
Any ideas? Thanks...
I found that if I deploy the RuleApp from a 'Rule project for Decision Service', I get the same error. Can you deploy it from a RuleApp project which references a 'Standard Rule Project'? That should fix the issue.
When I push a patch to a remote repository via ssh, the first try fails with
me#bowler$ darcs push
~/Dokumente/Aufsaetze/ar_report
Pushing to "me#somewhere:/home/me/darcs_repos/ar_report"...
Mon Nov 17 10:13:38 CET 2014 me#somewhere.com
* automatisierung
Shall I push this patch? (1/1) [ynW...], or ? for more options: a
darcs failed: Couldn't fetch 0000000369b60776b9ae996a253f8a5a296927293faab87036846b34b0e710c9fc0f58429b'
in subdir inventories from sources:
thisrepo:/usr/home/me/darcs_repos/ar_report
cache:/home/me/.darcs/cache
HINT: I could not reach the following repositories:
/home/me/.darcs/cache
/usr/home/me/darcs_repos/ar_report
If you're not using them, you should probably delete
the corresponding entries from _darcs/prefs/sources.
Apply failed!
The second attempt works without problems. Does someone has a clue what's going on here?
After some investigation, this turns out to have gone away in darcs 2.8.5 whereas it was happening in darcs 2.8.4. My best guess is that it was an instance of this bug, but the connection wasn't obvious.
yesterday I tried to merge a fork and my main branch for a school project. What I usually do is:
Clone my main branch
Merge them
If successful pull the commit of the new branch which was used to merge, if unsuccessful restart
When I did merge the forked branch and the main one, I skipped (or forgot) to merge using a test branch. I guess you figure out what happened, I made mistakes when executing commands and was unsuccessful in my merge, by the time I noticed that, I had already committed.
Now here's a list of what I know:
The clean version of the branch is rev 30
I am unable to clone rev 30 as I receive this: abort: data/inc/presentation/view/PageIndexV.php.i#fc3df292e283: no node!
I have 3 heads for some reason.
I have tried to do hg update -r 30
I tried to revert too
These are my heads
changeset: 35:cf4f3f8519d2
tag: tip
parent: 30:fdb11c78eb12
user: Alexandre * <*#gmail.com>
date: Sat Jun 08 19:07:31 2013 -0400
files: .htaccess
description:
Modif .htaccess
changeset: 34:331201eaa5e2
parent: 30:fdb11c78eb12
user: Alexandre * <*#gmail.com>
date: Sat Jun 08 18:55:19 2013 -0400
files: inc/presentation/view/PageIndexV.php
description:
Test
changeset: 33:6f6f6d4226da
user: Alexandre * <*#gmail.com>
date: Sat Jun 08 18:04:11 2013 -0400
description:
Close branch
Rev 33 was where I tried doing hg commit --close-branch
On Rev 34 I thought maybe adding back the file it's complaining about would help so I added it back (it was not needed anymore so it was deleted)
On rev 35, cpanel had modified .htaccess so I committed it and for some reason it made a new head for no reason...
If any other bit info is needed, just ask, I'll gladly provide it.
I really want to go back or get a copy of revision 30, every bit of info is appreciated, thanks.
Here is what I ended up doing:
I deleted the .hg folder
Did hg init again
then force the pull as they were now unrelated using hg pull -f