I've been unsuccessful with having my build publish to the new Package Feed in TFS 15 RC2. I'm currently running TFS offline and using a local build agent. I've followed these instructions to no avail.
Since the last image in those instructions is cropped around the URL, and that URL was specific to VSTS online, I thought mine might be wrong. So I tried the following (none worked):
Using http://[computername]:8080/tfs/DefaultCollection/_packaging/{feedName}/nuget/v3/index.json
gives an error when it tries to prompt for input of credentials in
interactive mode.
Using http://[computername]:8080 gives a 404.
Using http://[computername]:8080/tfs gives same error as #1.
Using http://[computername]:8080/tfs/DefaultCollection gives same error as #1
Since some errors happened while trying to do an interactive prompt, I thought it might be a permission error. The following links give some information, but it seems like the Build Agent should already be in the right category for publishing permissions.
https://www.visualstudio.com/en-us/docs/package/feeds/common-identities
https://www.visualstudio.com/en-us/docs/package/nuget/auth
Anyone happen to know a solution? Thanks!
EDIT
The build agent was running as NT AUTHORITY/Network Service, which is the default of the agent config. I removed this agent and configured it to run under my user account, which is an admin on the system. After doing so, I was able to publish without issues to the Packages using the URL in #1 (as Cece below has written). Is there something else I need to do to get the permissions set for the default agent?
The Internal Feed URL is the NuGet Package Source URL for the feed you want to publish to.
When you create a new Feed, navigate to your feed, and select Connect to feed. You'll see the NuGet package source URL. The format should be like: http://{tfsserver}:8080/tfs/DefaultCollection/_packaging/{FeedName}/nuget/v3/index.json
Related
I already have a website running and want to install JIRA Server on it. So how do I add a sub directory to my main website, example www.mywebsite.com is my actual website so want www.mywebsite.com/Jira how do I achieve this?
I had downloaded the windows JIRA Installer and ran it locally connecting to the database hosted on my server and it worked using localhost(http://localhost:8080/secure/Dashboard.jspa) however now I want to access it through the web link i.e base URL.
I am new to this so any help would be really appreciated.
Well I understand you do have a domain and you want to run your JIRA with context path /jira un that domain. If that's the case, you may need to consider running your JIRA behind proxy. Take a look at Atlassian documentation since it contains all the information that you need for this:
https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html
Is there a way to get the hudson job initiated user name.
Is it possible to get using script shell, py etc.
Lets assume I have the build # which was initiated. I know how to get the latest build info using api but would like to get a user details for a specific job.
Do you think, this will work for hudson? :)
https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin
Thanks in advance
That plugin will not work with Hudson, unless you download a very old version of the plugin. I'm not sure how many people are still using Hudson and haven't upgraded to Jenkins.
Anyway, when a user manually triggers a build, this is called a "user cause"; there are other types of cause, e.g. SCM trigger.
You can use the JSON or XML API to get the causes for a build, for example:
https://ci.jenkins-ci.org/job/remoting/lastSuccessfulBuild/api/xml?xpath=//action/cause/userId
In this case, this returns the username that caused the build to run.
Though note that there may be multiple causes for a build, and potentially other cause types that use the userId field.
This works in Jenkins, but it should also work in Hudson, but I haven't tested it.
I got a brand new Jenkins machine running on Linux Ubuntu. I use HTML Publisher Plugin to publish my html reports. I also use Jsystem to invoke the test scenario.
Jenkins 1.643
Html Publisher Plugin 1.10
At the end of the test when open the latest html report from the project main page I get this error:
Checksum mismatch
The checksum of the current wrapper file (0dd0c5ec07dff1d7179f03b5deb290e96ac68f8c) does not match the recorded checksum (090f21ac5f8c4b0eed9e789145a2fe2a6134c900). This indicates a possible security issue, therefore Jenkins will not serve this file. You can access the archived HTML files here.
I have checked existence of file and permissions. If I open the report from the job page then everything works.
UPDATE:
When I open the report from the job page I have no CSS and many errors.
Looks like a security issue.
UPDATE 2:
CSS and Javascript are back, Jenkins had an update on their Content Security Policy. Added args to the Jenkins startup scripts. First issue is still on. :(
It is a bug in that version of the HTML publisher plug in. The bug happens if you have more than one report in your job, mark the publishing option: 'Keep past HTML reports' and then click on the second report.
https://issues.jenkins-ci.org/browse/JENKINS-32281
Solution in https://jenkins.ci.cloudbees.com/job/plugins/job/htmlpublisher-plugin/61/.
Solution is released as 1.11 of the plug in.
it worked for me: Blocked script execution in <URL>. because the document's frame is sandboxed and the 'allow-scripts' permission is not set
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "")
I am not able to display the jenkins homepage properly.
I have installed two VM with jenkins server and accessing the jenkins through putty and windows browser. Scenarion of two jenkins are
with normal connection [working]
in vpn connection [not working]
i can view the homepage of 1st, but not getting proper view of 2nd machine.
It displays only text not working. I mean only texts of login ,logout and build now etc.
when i click on this text getting following error
"Not Found
The requested URL /login was not found on this server."
There is no browser issues i have tried it 2-3 browsers.
I think this is jenkins issues or something else plz help.
You share so few details about how you installed Jenkins and what is the environment that you should not expect any good answers. I suspect the problem is around the correct use of the Jenkins --prefix command line parameter. It changes the way Jenkins constructs URLs for links. I hope this helps. If not, you should consider telling us more about your setup.
I am currently using TFS to source changes to a web site code base. Currently, when I'm done making a change, I need to deploy the changes to a web server for review by the end user.
Generally the way I would do this is just connect to that machine via RDP, open visual studio and get latest to pull changes...
However, this only works if I'm the only one working on the entire site. If someone else RDP in to make changes, the site is locked to my TFS account, and they can't make any changes to it...
They could pull their own copy of the site into their own machine via TFS and check in the changes there but because so much of their part is done on the database (vs code) they'd have to duplicate everything they do into the website every time them commit a change, so they prefer to work directly on the machine...
is there any way to make this work, a better way to set this up so I can pull their changes into my local copy via TFS?
my biggest problem to overcome is the fact that when I Get Latest on the webserver via RDP it locks the entire solution to my TFS account, so that when they login to RDP with their credentials, they can't make any changes because the files are checked in, and of course they can't checkout because of course the solution is tied to my account.
If I can get past that I think we'd be okay.
any info is appreciated, please let me know if I can provide more context, thanks
Can you set up a different TFS workspace for each user on your RDP machine? This should allow multiple users to use the TFS client to pull the same solution on the same machine without issue.