To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.
ProM package repository
This morning, Eric Verbeek send the following message on the ProM Developers mailing list:
Dear all,
As mentioned last week, we now have a new repository (https://svn.win.tue.nl/repos/prom), a new trac site (https://svn.win.tue.nl/trac/prom), and a new Hudson server (http://svishudson.win.tue.nl:8080) (note that I forgot the :8080 last week, which may have lead to some confusion). Please recall that the Hudson server will build all downstream packages as well when a stable package gets changed in the repository, and that this build might take considerable time for some packages (Log, for example).
A package repository containing all packages from the new SVN repository is now also available: http://prom.win.tue.nl/ProM/packages/6.1/packages.xml . I’ve changed all (as far as I know, please let me know if I’ve missed some) ProM.ini files accordingly. If you want to load the latest packages, it might be a good idea to remove the .ProM folder from your user folder first, and then to install the “AllPackages” package using the ProM Package Manager. The “AllPackages” package replaces the “BPM2010” package. Please note that this package does contain a simple plug-in, which lists the packages and plug-ins which have been installed. Might be of use when you think not all packages/plug-ins have been installed.
Note that the package repository uses a subrepository for every package. The file for this subrepository is created every time Hudson builds the package, and it is released when the corresponding Release project is run. You can change the file by editing the build.xml file. In the build.xml file, look for the echoxml tag, which contains the contents for the subrepository file. By changing this part of the build.xml file, you’ll change the contents of the subrepository package file. Also note that the build.xml file contains the version number of the package (for the time being, all version numbers are set to “6.1.0”). Please update the version number once you’ve released the package (by running the corresponding Release project), as hudson does not auto-increment this number.
Also note that in the main repository file some subrepositories are commented out. These subrepositories do not exist yet as the package fails to compile. Please let me know as soon as the package compiles, so I can removed the comments.
Finally, today’s lunch meeting is herewith canceled.
Cheers,
Eric.
Dear all,
As mentioned last week, we now have a new repository (https://svn.win.tue.nl/repos/prom), a new trac site (https://svn.win.tue.nl/trac/prom), and a new Hudson server (http://svishudson.win.tue.nl:8080) (note that I forgot the :8080 last week, which may have lead to some confusion). Please recall that the Hudson server will build all downstream packages as well when a stable package gets changed in the repository, and that this build might take considerable time for some packages (Log, for example).
A package repository containing all packages from the new SVN repository is now also available: http://prom.win.tue.nl/ProM/packages/6.1/packages.xml . I’ve changed all (as far as I know, please let me know if I’ve missed some) ProM.ini files accordingly. If you want to load the latest packages, it might be a good idea to remove the .ProM folder from your user folder first, and then to install the “AllPackages” package using the ProM Package Manager. The “AllPackages” package replaces the “BPM2010” package. Please note that this package does contain a simple plug-in, which lists the packages and plug-ins which have been installed. Might be of use when you think not all packages/plug-ins have been installed.
Note that the package repository uses a subrepository for every package. The file for this subrepository is created every time Hudson builds the package, and it is released when the corresponding Release project is run. You can change the file by editing the build.xml file. In the build.xml file, look for the echoxml tag, which contains the contents for the subrepository file. By changing this part of the build.xml file, you’ll change the contents of the subrepository package file. Also note that the build.xml file contains the version number of the package (for the time being, all version numbers are set to “6.1.0”). Please update the version number once you’ve released the package (by running the corresponding Release project), as hudson does not auto-increment this number.
Also note that in the main repository file some subrepositories are commented out. These subrepositories do not exist yet as the package fails to compile. Please let me know as soon as the package compiles, so I can removed the comments.
Finally, today’s lunch meeting is herewith canceled.
Cheers,
Eric.
Joos Buijs
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Comments
-
Hi I'm new about ProM development. The Hudson server does not work for the workshop.
-
Hi,The Hudson project for the workshop is accessible at http://ais-hudson.win.tue.nl:8080/job/Workshop/. However, most likely, you are not allowed to trigger any builds for the projects, nor are you allowed to commit any changes into the workshop project.Please note that the hudson server is now at http://ais-hudson.win.tue.nl:8080, and not anymore at http://svishudson.win.tue.nl:8080.If you have checked out the workshop project (from https://svn.win.tue.nl/repos/prom/Packages/Workshop/Trunk) on your local computer, please continue working on it locally.Kind regards,
Eric. -
ok thank you
Howdy, Stranger!
Categories
- 1.6K All Categories
- 45 Announcements / News
- 225 Process Mining
- 6 - BPI Challenge 2020
- 9 - BPI Challenge 2019
- 24 - BPI Challenge 2018
- 27 - BPI Challenge 2017
- 8 - BPI Challenge 2016
- 68 Research
- 1K ProM 6
- 393 - Usage
- 287 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame