Steps for setting Jenkins/Bitbucket CI environment in Windows - little trickier than Linux
1) Download and Install Jenkins-2.60.1(current as of the day written)
2) Once installed changed the port from C:\Program Files (x86)\Jenkins\jenkins.xml to ‘9090’ and
restart jenkins
3) Set security options to “false” from config.xml
4) Then open localhost:8090 and see if you can see Jenkins Interface
5) Install all default plugins plus following plugins to work Jenkins correctly with Bitbucket and
dev requirements for my workflow
a. Bitbucket pull request builder plugin
b. Maven integration plugin
c. MS build plugin
d. Next build number plugin
e. NodeJS plugin
f. SSH Agent Plugin
g. SSh plugin
h. Self-organizing swarm plugin
i. Categorized view plugin
j. Publish-over ssh
k. Schedule build
l. Nugget
m. Vagrant
6) Install git bash in the machine
7) From git bash, generate ssh-keys , ssh-keygen
8) Add the public key(id_rsa.pub) in BitBucket under group account
Friday, July 21, 2017
Thursday, May 26, 2016
Setting up automatic product or build version increment using JENKINS for .NET projects
Steps for setting up automatic product or build version increment using JENKINS Continious Integration server and Visual Studio for .NET projects
Part A - Configure Visual Studio Solution
1. Copy the "AssemblyInfo.cs" from your project solutions and rename into "AssemblyInfo.cs.template"
2. Add a file called "AssemblyInfo.cs.template" and replace with these two lines:
Part A - Configure Visual Studio Solution
1. Copy the "AssemblyInfo.cs" from your project solutions and rename into "AssemblyInfo.cs.template"
2. Add a file called "AssemblyInfo.cs.template" and replace with these two lines:
[assembly:
AssemblyVersion("#VERSION_NUMBER#")]
[assembly:
AssemblyFileVersion("#VERSION_NUMBER#")]
3. In project properties, insert this pre-build command:
"$(SolutionDir)builder-scripts\templates\pre-build\Stamper.exe"
"$(ProjectDir)\"
4. Put the "builder-scripts" folder into your solution
folder. Builder scripts source
Subscribe to:
Posts
(
Atom
)