[JIRA] (JENKINS-14588) Cannot query a job's git branch through xml api
Jason Marshall commented on JENKINS-14588 Cannot query a jobs git branch through xml api I have the same problem with other fields in the GitSCM object. Despite being processed in the constructor and exposed via @Exported, they return empty lists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14588) Cannot query a job's git branch through xml api
Jason Marshall edited a comment on JENKINS-14588 Cannot query a jobs git branch through xml api I have a similar problem with other fields in the GitSCM object. Despite being processed in the constructor and exposed via @Exported, they return empty lists. I filed a bug covering the 'repositories' field as JENKINS-16558 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16558) Cannot get the repositories from the git plugin via the API
Jason Marshall
created JENKINS-16558
Cannot get the repositories from the git plugin via the API
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
30/Jan/13 7:53 PM
Description:
I'm trying to write a plugin that needs information from SCM plugins.
I'm having trouble extracting information from the Git plugin. I think it has some bugs that are causing it to not report data even though there's a great good deal of code in there to generate the answers.
Specifically, I can't find any incantation of scm/api/json that returns useful data in the repositories attribute. It seems to be an empty list. JENKINS-14588 reports that the 'branches' field is also empty. I'm curious if the root cause is similar for both or if they're separate issues.
{
"browser" : null,
"type" : "hudson.plugins.git.GitSCM",
"branches" : [
{
}
],
"mergeOptions" : {
"mergeRemote" : null,
"mergeTarget" : null,
"remoteBranchName" : null
},
"repositories" : [
{
}
],
"userRemoteConfigs" : [
{
"name" : "",
"refspec" : "",
"url" : "ssh://git-server:29418/projectname"
}
]
}
Project:
Jenkins
Labels:
plugin
scm
plugins
Priority:
Major
Reporter:
Jason Marshall
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16559) Build api doesn't include git repository
Jason Marshall
created JENKINS-16559
Build api doesnt include git repository
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
30/Jan/13 8:28 PM
Description:
If you pull the JSON for a build, you will see the branch name and the SHA1 hash for the commit but you won't see the repository url anywhere.
This makes life difficult if you're trying to watch more than one project, as you can't disambiguate by the repository.
{
"buildsByBranchName" : {
"origin/master" : {
"buildNumber" : 1813,
"buildResult" : null,
"revision" : {
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"branch" : [
{
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"name" : "origin/master"
}
]
}
},
"origin/mri" : {
"buildNumber" : 50,
"buildResult" : null,
"revision" : {
"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513",
"branch" : [
{
"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513",
"name" : "origin/mri"
}
]
}
}
},
"lastBuiltRevision" : {
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"branch" : [
{
"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6",
"name" : "origin/master"
}
]
},
Project:
Jenkins
Labels:
jenkins
git
build
scm
Priority:
Major
Reporter:
Jason Marshall
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13540) Redirects do not work properly on IE
Jason Marshall created JENKINS-13540:
Summary: Redirects do not work properly on IE
Key: JENKINS-13540
URL: https://issues.jenkins-ci.org/browse/JENKINS-13540
Project: Jenkins
Issue Type: Bug
Components: other
Affects Versions: current
Environment: Internet Explorer
Reporter: Jason Marshall
TL;DR: Make the 404 redirect page longer so IE behaves, or change how
redirects work.
Let's say you have a build with no test reports (eg, a cancelled build). Try
to enter the testReport page:
http://jenkins:8080/job/MyProject/1325/testReport/
Jenkins will perform a 302 Found redirect to
http://jenkins:8080/job/MyProject/1325/testReport/?
This will load a 404 page with the following contents:
htmlheadmeta http-equiv='refresh'
content='1;url=..'/scriptwindow.location.replace('..');/script/headbody
style='background-color:white; color:white;'Not found/body/html
On Chrome and Firefox this will redirect to
http://jenkins:8080/job/MyProject/1325 which is probably what you expected. IE
will not. It will instead redirect to its own internal 404 page.
I think this page purports to tell why this happens. It says that the page
needs to be 512 bytes or it's ignored:
http://www.404-error-page.com/404-error-page-too-short-problem-microsoft-ie.shtml
The upshot is that it would be good if either both redirects used a 302 Found,
or perhaps a simpler solution would be if the 404 meta-redirect had more
content so that Explorer took it seriously.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
