1. Download the installation files for one or more plug-ins from the following site: https://developer.ibm.com/urbancode/plugins/ibm-urbancode-build/. Do not extract the compressed files.
2. Load the plug-ins:
   1. From the IBM UrbanCode Build user interface, click the System tab.
   2. In the Server group, click Plug-ins.
   3. On the Plugins page, Browse and locate the plug-in installation file and then click Open.
   4. On the Plugins page, click Load.

Results

After the upload to the server is complete, the plug-in is listed on the Plugins page and available for immediate use.

Uninstalling a plug-in

To uninstall a plug-in, click System > Plug-ins, locate the plug-in, and then click the Delete icon.

Note: Before uninstalling a plug-in, verify that it is no longer in use. Deleting a plug-in which is being used by existing processes causes those processes to be invalid.

The post How to Install plug-ins in IBM UrbanCode Build appeared first on scmGalaxy.

• ZIP file
• RPM
• Debian
• Docker

In this tutorials, I am talking about Zip file Based installation only.

Before You Proceed, You must do following.

1. Take a Backup of System config using “System Export”
Artifactory can export and import the whole Artifactory server: configuration, security information, stored data and metadata. The format used is identical to the System Backup format. This is useful when manually running backups and for migrating and restoring a complete Artifactory instance (as an alternative to using database level backup and restore).

Please follow the instructions out here https://www.jfrog.com/confluence/display/RTF/Importing+and+Exporting

2. Back up your database.

3. JDK Version – From version 4.0, Artifactory requires JDK 8. If your current version is v3.x, before you upgrade to Artifactory 5.x, please make sure you install JDK 8 and update your JAVA_HOME environment variable to point to your JDK 8 installation.

4. Repositories with Multiple Package Types – From version 4.0, Artifactory will only index, and work with corresponding clients for single package type repositories. If your current version is 3.x and the installation includes repositories that support multiple package types, you need to migrate them to single package type repositories.

Upgrading from version 4.x or 5.x to the latest version is a simple procedure.

Step 1 – Unzip the Artifactory distribution archive.
Step 2 – If the $ARTIFACTORY_HOME/tomcat/conf/server.xml has been modified keep it in a temporary location.
Step 3 – Backup files to a temporary location according to the conditions described below:

• In all cases, backup $ARTIFACTORY_HOME/bin/artifactory.default
• If Artifactory is configured to work with a database that is not Derby, backup the $ARTIFACTORY_HOME/tomcat/lib/<JDBC> driver.

Step 4 – Remove the following files and folders from your $ARTIFACTORY_HOME folder:

• webapps/artifactory.war
• webapps/access.war
• tomcat
• bin
• misc

Step 5 – Replace the removed files and folders with the corresponding ones from the new unzipped version.

Step 6 – Any files that were stored in temporary locations should now be returned to their original location under the new installation.

Step 7 – If you installed Artifactory as a service, you now need to run the service

• For a Linux service, browse to $ARTIFACTORY_HOME/bin and execute the following command as root: $ARTIFACTORY_HOME/bin/installService.sh [USER [GROUP]]
• For Windows service, browse to %ARTIFACTORY_HOME%\bin. First uninstall the service by running uninstallService.bat, then reinstall the service by running installService.bat. You can now run the service through the Windows UI or as described in Running Artifactory.

Reference
https://www.jfrog.com/confluence/display/RTF/Upgrading+Artifactory

The post Upgrade Artifactory from Open-Source (OSS) to PRO? appeared first on scmGalaxy.

after moving our Sharepoint and Database to another server (with changing the servername), I have the problem, that after installing 7.0 SP3 from scratch, the process “Upgrade Registry Types” in the Repository Manager is still pending no matter how often I click on “Run”
All other parts or modules of WPS are working well.

Any help is highly appreciated.

applicationPackaging replied the topic: Re: Upgrade Registry Type 7.0 SP3
Check the Altiris knowledgebase ( kb.altiris.com ) as there are some articles about repository manager issues which may help. If that does not solve your problem, then I would recommend making a call to Wise support as they have more information internally on these sorts of issues and may be able to help you solve this quickly.
I assume you have checked the sharepoint for INI files in case of any hard coded UNCs to the old server name. If you have SQL query skills then you could also check the Wise sql databases for any references to the old server.

The post Upgrade Registry Type 7.0 SP3 appeared first on scmGalaxy.

“If you are still using the WISE Installation System to develop your installations, you probably know that Symantec announced the
end-of-availability of WISE Installation Studio and WISE Installation Express. An era comes to an end.

Symantec does no longer accept orders for new licenses of WISE Installation Studio or WISE Installation Express. In addition, Symantec does no longer accept renewals for maintenance agreements related to WISE Installation Studio.

If you are concerned your WISE product doesn’t support your software deployment requirements, consider a jump to SetupBuilder Developer Edition.

Looking to target Windows 7, Windows Vista and Windows Server 2008? We’ve got you covered! We are committed to providing you with support for the latest advancements in installation, deployment and operating system technology!

Discover why more and more Wise users are making the switch to SetupBuilder:
www.lindersoft.com/products_setupbuilder_dev.htm

For users who want to move over from WISE Installation Studio to SetupBuilder, there is currently a special offer:

Switch to SetupBuilder 7 Developer Edition including a full 1-year maintenance and support subscription plan and pay only $245 instead of $399.

This special offer expires June 30, 2010

Contact our Sales at sales@lindersoft.com to save 40% off your move to SetupBuilder Developer Edition.

Note: Special offer only available to customers moving over from WISE Installation Studio, providing proof of ownership.

The post Special Upgrade for WISE Installation Studio customers appeared first on scmGalaxy.

Hi all,

I’m proud to announce the availability of a new release of Sonar
PDF Report Plugin (Commercial edition):
http://blog.klicap.es/products/sonarpdfreportplugin

Key features of this new release:

* Include information provided by other installed plugins
* Possibility of use SVG images in front page and header

Actually Sonar PDF Report Plugin 2.1 supports integration with:
* Technical Debt Plugin
* SIGMM Plugin
* Total Quality PLugin
* Quality Index Plugin
* Taglist Plugin

Regards,
Antonio.

The post Sonar PDF Report Plugin 2.1 – What is new in Sonar PDF Report Plugin 2.1? appeared first on scmGalaxy.

This document will help you upgrade Continuum from 1.2.x to 1.3.3 and above.

When upgrading Continuum, it could have some database model changes. Usually these changes will be migrated for you, but in some cases you may need to use a backup from the previous version and restore that data into the new version. The Data Management tool exports data from the old database model and imports the data into the new database model.

If you had used the APP_BASE environment variable in Continuum 1.2 to differentiate your configuration from the installation, you should rename it to CONTINUUM_BASE in Continuum 1.3.

Note: The Jetty version in Continuum 1.3.4 and above has been upgraded to 6.1.19. When upgrading to Continuum 1.3.4 or higher, there is a need to update the library contents listed in $CONTINUUM_BASE/conf/wrapper.conf with the ones included in the new distribution especially if the $CONTINUUM_BASE directory is separate from the installation.

Using Backup and Restore to upgrade

There are 2 databases that need to be considered: one for the builds and one for the users.

There were no changes in the users database from 1.2.x to 1.3.2, so you can simply point Continuum 1.3.2 at your existing user database.

The builds database has had model changes, and will need to be exported and imported.

First, download the Data Management tools you will need. The tool is a standalone JAR that you can download from the central repo.

You will need to download two versions of the tool, one for the export out of the old version and one for the import into the new version:

Note: The 1.2, 1.2.2 and 1.2.3 released versions of this tool have a bug. To export databases from 1.2.2 or 1.2.3, you will need to use version 1.2.3.1 of the tool. To export databases from 1.2, you may use the 1.1 version of the tool.

• http://repo1.maven.org/maven2/org/apache/continuum/data-management-cli/1.3.2/data-management-cli-1.3.2-app.jar
• http://repo1.maven.org/maven2/org/apache/continuum/data-management-cli/1.2.3.1/data-management-cli-1.2.3.1-app.jar
• http://repo1.maven.org/maven2/org/apache/maven/continuum/data-management-cli/1.1/data-management-cli-1.1-app.jar

Next, follow these steps to export data from the old version

• Stop the old version of Continuum
• Execute this command to create the builds.xml export file

java -Xmx512m -jar data-management-cli-1.2.x-app.jar -buildsJdbcUrl jdbc:derby:${old.continuum.home}/data/databases/continuum -mode EXPORT -directory backups

Then, follow these steps to import the data to the new version

• Start the new version of Continuum to create the new data model, but do not configure it.
• Stop Continuum
• Execute this command to import the builds data from the xml file you created earlier:

java -Xmx512m -jar data-management-cli-1.3.2-app.jar -buildsJdbcUrl jdbc:derby:${new.continuum.home}/data/databases/continuum -mode IMPORT -directory backups -strict

Note: Remove -strict when importing data from 1.3.1 to 1.3.x to ignore unrecognized tags due to model changes.

Finally, be aware that sometimes the NEXT_VAL values in the SEQUENCE_TABLE need to be adjusted.

• Before starting Continuum for the first time after the import, connect to the db with a client like Squirrel SQL and check the values in the NEXT_VAL column of the SEQUENCE_TABLE.
• Values must be greater than the max id value in each table.
• For example, the next value of “org.apache.maven.continuum.model.Project” must be greater than the greatest id in Project table.
• Here are some example SQL statements. You may need to add or remove lines depending on the contents of your database.

UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(systemconfiguration_id)+1 from SYSTEMCONFIGURATION) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.system.SystemConfiguration';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from BUILDQUEUE) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.BuildQueue';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from SCHEDULE) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.Schedule';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from BUILDDEFINITION) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.BuildDefinition';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from LOCALREPOSITORY) WHERE SEQUENCE_NAME='org.apache.continuum.model.repository.LocalRepository';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from PROJECTGROUP) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.ProjectGroup';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(scmresult_id)+1 from SCMRESULT) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.scm.ScmResult';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(projectdependency_id)+1 from PROJECTDEPENDENCY) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.ProjectDependency';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from BUILDDEFINITIONTEMPLATE) WHERE SEQUENCE_NAME='org.apache.maven.continuum.model.project.BuildDefinitionTemplate';
UPDATE SEQUENCE_TABLE set NEXT_VAL = (select max(id)+1 from ABSTRACTPURGECONFIGURATION) WHERE SEQUENCE_NAME='org.apache.continuum.model.repository.AbstractPurgeConfiguration';

Now you can start your new version of Continuum.

Reference: http://continuum.apache.org/docs/1.3.6/installation/upgrade.html

The post Upgrading Continuum – Continuum Upgradation Guide appeared first on scmGalaxy.