I currently have a Bamboo task that invokes jspm install from my local app's node_modules installation of jspm but the registry is missing.
The task errors out with "Registry bitbucket not found"
I assume this is because it's installing jspm in the scope of just the task and from that viewpoint the registry is never instantiated.
This is a new issue for me though and just recently started happening after I installed bamboo as a service. Previously, I had set up the registry local to the machine and it seems to have picked it up.
I don't have a working state that I can really revert back to however.
Has anyone else experienced issues with jspm registries in CI server tasks?
Update 1: I stuck a little sanity check in there to execute node -e "console.log(process.env.LOCALAPPDATA || process.env.HOME || process.env.HOMEPATH)" since this is where it looks for the global config anyways and found that the variable that gets used here is not always the same. Sometimes it's my user home (desirable) and other times it's the system's home path (undesirable).
This is the part that's telling of what the issue is:
This is a new issue for me though and just recently started happening
after I installed bamboo as a service. Previously, I had set up the
registry local to the machine and it seems to have picked it up.
Checking what user it was set to use in the services revealed that it was configured to use the local system account which is incorrect. Changing to use the properly configured user account resolves the problem.
Related
I have a fresh build server and need to setup jenkins there. So I created a first user on the Mac mini, and used that user to install Jenkins on the machine.
Jenkins then created another user (Jenkins) on the Mac Mini.
I thought that correct way to proceed is to login as that Jenkins user (with Admin rights) and prepare the build environment as this Jenkins user.
But I cant install Visual Studio for MAC, cant install SourceTree... bcs even though Jenkins has Admin rights, I am getting
"You do not have permissions to open the application 'Install Visual
Studio for Mac' contact your administrator..." message.
But as I said the Jenkins user is Admin user. So am I doing it wrong? What user should prepare all the build tools? And if it is supposed to be the first user I created (after booting the Mac mini for the 1st time), how do I let Jenkins use the apps then? When I tried doing this on my macbook, jenkins couldnt use some of the build tools, bcs apparently it did not have the permissions to do so.
So what is the correct way to set up a jenkins environment, so I can install whatever tools I need, and Jenkins can use these during builds/deploys?
Any help appreciated, all the guides about jenkins speak of jenkins user, but none gave me an idea what is the best way to set this all up.
My 2 cents.
I have not worked with MAC. So some of my assumptions may be wrong or suggestions may be not applicable to you.
I have set up Jenkins mostly on Linux and a couple of times on Windows. I used to install Jenkins using the RPM package which, upon installation, will create a 'jenkins' user and group.
For start/stop/restart, I always use 'sudo' since Jenkins is installed as a service.
Other build related tools like Java, Maven etc, I always make sure that Jenkins can access them and execute them. ie, I give execute privilege on those tools.
The JENKINS_HOME directory, I used to create a symbolic link from the default home directory to a file system with enough storage. I will do the same for Jenkins log file.
The benefit of having those Jenkins/tool files/directories as part of a custom defined directory structure is that I do not need to remember installation paths of each tool. ie, I have my Jenkins, maven, java, sonarQube everything under a directory I know. Even if I set up these tools in different servers, I will stick to the same directory structure.
My suggestions to you.
Setup build tools which are to be used/accessed from Jenkins, set them up with your 'first user' and give execute privilege to Jenkins user/group.
Create a directory 'ci' and link or place all tools inside. You can further have subdirectories for app - for binaries/installed files, data - for generated data like Jenkins_home, log - to keep log files of these tools.
ci/jenkins
ci/sourcetree
ci/apache-maven
Suggestion 2 is initially time-consuming but it will save a lot of your time as you use the tools on a daily basis.
I'm having some trouble getting an Octopus Tentacle to deploy a package.
It keep telling me that the Tentacle may not have enough permissions to access the application. The tentacle service is running under the Local System account.
All the files I expect there to be are present and unpacked from which I would assume everything is working as it should.
The tentacle is working fine. The log files don't show any errors and no information that could give me a hint why this is happening.
I must have configured something wrong or have forgotten something but I can't figure it out
The executing users have full control on the folder. Actually I set it to everybody full control to be sure it's not a permission issue.
I'm new to DevOps and build/automation tools. I installed Apache Maven and Jenkins, but the Jenkins dashboard is not popping up. In other words, I should be seeing this:
But I'm instead seeing this:
I found a similar question here, but I was unable to understand what to do: How to access Jenkins dashboard locally when it is installed on staging server?
From what I understand, I need to make Jenkins open up on a different port, but I'm not sure how to do this. I checked in services and I can confirm that Jenkins is in fact running.
Ok, so I figured it out, but I still don't understand what that Apache page is. For anyone wondering how to fix the issue with the dashboard not popping up:
STEP 1: I was exploring the installation directory and found a file called jenkins.xml with the line --httpPort=8080.
STEP 2: It wouldn't let me edit and save the file so I dragged it to my desktop where it let me make changes. I changed 8080 to 8082, saved, and then placed the file back in the installation directory.
STEP 3: I didn't notice any changes until I restarted the Jenkins service and it's showing the dashboard now.
I still would like to know what that "Apache 2 Ubuntu Default Page" is about.
The Heroku Toolbelt's login prompt has started causing my continuous integration job to fail. I'm guessing something changed in a recent version, but since this project had been on the back-burner for a few months, I'm not sure exactly when that happened. I'll also admit that I don't remember how I had this working in the first place. It's possible that I did something similar to my answer below, but have no recollection of that.
Is there any way to script completion of the login prompt or bypass it entirely using environment variables/config?
Version information:
heroku-toolbelt/3.42.40 (x86_64-linux) ruby/2.2.2
heroku-cli/4.27.26-693efcb (amd64-linux) go1.6
I've tried manually logging into Heroku on the CI server, which creates a .netrc and copying that into my image, but it appears to be ignored.
Unfortunately, the only solution I was able to come up with was to build the Docker image, create a container, run heroku login inside of it, commit the changes and use the new image in my CI workflow.
I'm in the process of setting up a proper CI environment and am currently evaluation TeamCity. (So my TeamCity experience is non-existent.).
I've performed a default install of TeamCity 5.0.1 Professional in a clean Windows XP (for now) VM.
I've created my project and pointed it to my source repository and queued up a build.
However, I don't see any Build Agents installed/available via the Team City web interface. I've checked and there is a 'Team City Build Agent' service installed and it's running. I've also reviewed the log files in the buildAgent folder and don't see anything that would lead me to an error.
Is there a step or concept that I'm missing here on getting the default Build Agent to become available to Team City? I'm not trying to do anything complicated with the build. (at this point, I just want to pull my source down from the repository)
I had exactly the same problem. After going through settings, reinstalling the agent etc, I found that the problem was rather simple - the TeamCity agent placed a wrong teamcity URL in it's property (and other paths as well).
Find the buildagent.properties file ( buildAgentInstallDir\conf\buildagent.properties), and you'll probably see that all of the lines have 'escape' characters in them (e.g. serverUrl=http://localhost:8090/ )
Modify the file to remove escape chars (i.e. links should be plain like: serverUrl=http://localhost:8090/ , env.TEAMCITY_JRE=C:\Program Files\TeamCity\BuildAgentInstalled\jre and similar)
Hope this helps...
If your server is running on a machine with multiple IP addresses, the agent may fail to identify the correct IP address. You can explicitly set the IP address in the buildAgent/conf/buildAgent.properties file. You should see a section that is optional to set the IP of the buildAgent and the IP of the Teamcity server. I recommend trying both.
Right after a clean install you should see one build agent - the local machine. I don't think this has anything to do with you even having to have a project defined. IMHO you something went wrong with the installation.
Filip
If you've changed the TeamCity server port in conf/server.xml like:
<Connector port="8222" protocol=".."/>
You should change the default agent configuration in buildAgent/conf/buildAgent.properties
serverUrl=http://SERVER-IP-HERE:8222/