I'm looking to a Jenkins (fka Hudson) plugin to visualize which revision number is connected to each build number (SCM is SVN, build done by maven).
Does anyone know of such a plugin?
Update1:
Yes, I know of svn tags, we use them, we can go to svn to understand this information - but it's a cumbersome way to understand which build includes my fix.
I use the description setter plugin with regex Updated to revision (.*) and description r\1
Related
I am new to sonar, i have installed sonarqube on RHEL 7 machine and its version is 5.1.1.
and the runner's version is 2.4.
I have four cpp related plugins, i tried with each one,
sonar-cxx-plugin-0.9.4-RC3.jar sslr-cxx-toolkit-0.9.4-RC3.jar
sonar-cpp-plugin-3.6.jar sonar-cpp-plugin-3.5.jar
sonar-cxx-plugin-0.9.jar
nothing seems to be listing the Sensor CxxCppCheckSensor . i need this for integrating cppcheck with the sonar. my cppcheck version is 1.68.
i have included sonar.cfamily.cppcheck.reportPath = in my sonar.project.properties file too.
Am I doing something wrong here ? Please help me out.
1.And do these cpp plugins needs license or trial key for proceeding?
2. Can cppcheck's xml report alone be viewed in sonar's dashboard?
Thanks in advance :)
sonar-cpp-plugin correspond to the commercial plugin and of course needs a license, sonar.cfamily.cppcheck.reportPath property is only for the commercial plugin.
sonar-cxx-plugin correspond to the community C++ plugin and has different properties.
Do not mix the two different plugins and documentation, pick one and follow one documentation installing only one of them.
One great feature of TravisCI is the ability to add a configuration file to your repository which describes how Travis should run your build. Is something similar possible with TeamCity?
I've done some pretty heavy configuration for enterprise TeamCity servers so I'm fairly well versed in it, but I've never seen or heard of this type of configuration and so far as I can tell it's not in the docs. I'd be okay with a plugin as well, assuming it's stable.
It seems this feature was requested some time ago and is being tested in a newer version of TC.
Full discussion: http://youtrack.jetbrains.com/issue/TW-2806
Relevant comment: http://youtrack.jetbrains.com/issue/TW-2806#comment=27-781368
Try out EAP, this feature is already there.
EAP is currently free http://confluence.jetbrains.com/display/TW/TeamCity+EAP+(Latest)
We have been trying to build wso2 (various products) from source to no avail.
I have looked for information all over (with assistance from Google) and followed the few instructions we have found but without luck.
I have, on the other hand, found various posts discussing this process and how error prone it is due to this or that.
Don't get me wrong, WSO2 looks like an amazing framework to work within but confidence in the project is not boosted by the complicated/error prone/enormous build process.
Does anyone here have a good description/recipes to build the 4.x.x version of carbon?
I really don't think it is intentionally hard to build. The product is huge with tons on developers working on it. Most of the issues seem to be around erroneous commits by developers. My understanding is that WSO2 will be changing the development process to make it more robust (source: Manoj's Comment).
The WSO2 set of products are awesome and well engineered. They can be built, but you will need to persist and resolve issues along the way.
It took me quite a few days to get a working build in my spare time. Here is a rough sequence of tasks to perform:
1) Checkout the 4.0.0 branch:
svn co https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
svn co https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
svn co https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
For more information of the code base high level structure, see here: what is wso2 'orbit', 'kernel' and 'platform'?
2) Decide which version of a product you need to build - Which version of patch-release to build?
3) Build the three separate code bases (build the main branch plus patch-release versions below your required version).
build orbit 4.0.0/ Then build orbit/patch-release/4.0.x
build kernel 4.0.0/ Then build kernel/patch-release/4.0.x
build platform 4.0.0/ Then build platform/patch-release/4.0.x
Note to build:
use Java 6 (Use Sun/Oracle JDK - not OpenJDK)
use Maven 3
set MAVEN_OPTS to -Xms512m -Xmx1024m -XX:MaxPermSize=1024m
you will probably need to use the following mvn command line: mvn clean install -Dmaven.test.skip=true
You will find the built distribution zip file here: ROOT/distribution/product/modules/distribution/target/ (source: WSO2 Carbon 4.1.x - how to make the distribution)
Be prepared to put in the time to hunt down and fixing issues as you encounter them. Most issues seem to be due to maven dependency issues. Using google, you can usually find the answer. Also you post any issues you need help with on stackoverflow.
I am a complete newbie to SBT and scala world. I wanna create a lift application and while exploring on how to do it i stumbled everywhere that i must use SBT. So i went to the github wiki page and followed the instructions for windows. I downloaded the jar given there and created sbt.bat and put both the files in c:\sbt and added it to my path. Then i went c:\liftprojects and typed sbt.
It did something but as given everywhere i expected a wizard of some sort which will ask me what kind of project i wanna build and stuff and generate the directory structure just like mvn:archetype:generate but it didnt do anything. It just ran some downloads and created two dirs
project
boot
blah
target
blah
target
scala 2.8.1
blah
in github wiki it says sbt follows maven bir structure but i cannot see it here.
Am i doin something the wrong way. Im stuck on this. All i need is to know how to create a lift app or a scala project.
To get started with Lift 2.4 my recommendation is to clone the examples repository
git clone https://github.com/lift/lift_24_sbt
Then you can use one of the project templates in that repo, with both 2.8 and 2.9 Scala versions. For example, a good way to start with Lift is using the basic project (with Scala 2.8.1 in this example)
cd lift_24_sbt/scala_28/lift_basic/
Start sbt by typing
./sbt
On Windows use sbt.bat. Inside the sbt console, type
update
jetty-run
Open a web browser and point it to http://localhost:8080 to open the Lift application. To stop the application server, simply type jetty-stop.
You can use this template project, or the other templates in that repo, as a starting point for your applications.
Lift wiki contains a lot of useful information. Specifically, you can follow the instructions getting started section here.
I am about to start a new personal project. It aims to be a pretty big one so I thought it would be a good idea to keep some sort of CVS. I have also read lot of interesting stuff about unit testing and I would like to include some system that automatically builds the project and runs a series of test after each check in.
The characteristics are:
Only one developer and one machine (just me and my computer!).
Include a CVS.
Include automated testing.
The software should be free (as in no-cost) and run under Linux.
It is going to be C++ and ANTLR based.
So far, I have set up SVN and Eclipse+CDT+ANTLR for development but I am pretty lost about the automated build+test setting. To write the tests I have been thinking in Boost.Test or UnitTest++.
So that's the source of my question. How should I set up my local test/build machine?
Links to valuable tutorials are more than welcome.
Thanks.
It seems that most open source continuous integration servers are built on java and does not support C++ "out-of-the-box". However there are some links you can start with (note that for running most open source continuous integration servers you need a java environment):
What continuous integration tool is best for a C++ project - some alternatives for continuous integration software
Continuous integration for C++ - some ideas for Hudson configuration
Using CruiseControl with C++ - some ideas and configurations for CruiseControl
Compiling C/C++ code with Ant - if you do use the "Makefile project" in CDT and do not want to use make as a build tool
I personally prefer Hudson because of its simply install (no need for application server just start with java -jar hudson.war) and easy to use and quite "clever" gui. Hudson can checkout your code from SVN (or CVS) and can run a shell script or Ant file as a build script. Maybe you have to spend a few days to set up a configuration with a proper build script but I think it worth the time.
The sort of automatic process you are looking at is called continuous integration. There is software to help you with this - a good example is JetBrains TeamCity. You will also hear of people using CruiseControl, Atlassian Bamboo and so on for this.
To take full advantage of this, you may also want to look at an automated build tool like Ant or Mavenl; your continuous integration build will then use this as its build runner.
A good starting point would be the Martin Fowler page on CI or the Wikipedia one.