When I try to update my VM that host my tuleap forge with yum tools, I lost access to the drop-down menus of the forge web interface.
I can just rollback to the last snapshot to solve this problem. Is a way to keep the forge up to date exist?
Did you follow this guide to proceed to the update? Try to issue a service httpd restart to see if it fixes your problem. If not, delete the file you will find at /usr/share/tuleap/src/www/scripts/combined/*.js and
service httpd restart and then reload your page.
If you follow correctly the instructions in the guide you should be able to update smoothly.
Related
I`ve created a new user and set that as an administrator but still failed to log in after times of trial. However, I find some information in console, but can not solve it after enable-disable plugins and multiple times of re-installation of rabbitmq-server.
BTW I am using CentOS 7.9.
Solved the question by changing browser from chrome to IE, edge also works.
I'm running jira in openshift using the basic image from atlassian: https://hub.docker.com/r/atlassian/jira-software
So far most things work fine.
I installed a plugin using the web ui which worked as well.
But now I'm running into an issue when a pod is restarted. The pod uses the image and naturally (as specified) my plugin is not installed anymore. I can install the plugin via webservice calls and register it as an osgi module for jira. But I don't want to do this manually. Building a pipeline or jon for this is quite easy (I'm thinking jenkins or ansible tower). But I so far I didn't find a way to trigger this pipeline after the pod is started (or better after jira is started).
Anyone got an idea how to handle this?
Thanks and best regards. Sebastian
Why not create a custom image based on the Atlassian image with everything you need installed?
As far as I know, there isn't a way to trigger a pipeline when a Pod is started; only Webhook, Image Change, and Config Change triggers are available. You'll need to write a Jenkinsfile to script all of the installation and setup you want, but then that can be triggered in one of the three ways mentioned.
I'm thinking an Image Change trigger would work best for you, so when the latest version of Atlassian's image comes out, you can run your pipeline to set everything up on the latest version.
Also, just curious, but do you have some persistent storage attached to the Jira pod? If not, you'll lose everything in Jira if the Pod dies; that means tickets, boards, comments, everything.
Update:
Looking at this page, it looks like most of the stuff you're trying to persist is stored in jira-home, so maybe mounting that as a persistent volume will be a good solution for you.
You're correct that the tickets are stored in the database, but I'm guessing the database connection settings are getting wiped when the Pod is cycled.
The jira-home directory stores your application and database connection settings, as well as a subdirectory for your plugins.
dbconfig.xml
This file (located at the root of your JIRA home directory) defines
all details for JIRA's database connection. This file is typically
created by running the JIRA setup wizard on new installations of JIRA
or by configuring a database connection using the JIRA configuration
tool.
You can also create your own dbconfig.xml file. This is useful if you
need to specify additional parameters for your specific database
configuration, which are not generated by the setup wizard or JIRA
configuration tool. For more information, refer to the 'manual'
connection instructions of the appropriate database configuration
guide in Connecting JIRA to a database.
jira-config.properties
This file (also located at the root of your JIRA home directory)
stores custom values for most of JIRA's advanced configuration
settings. Properties defined in this file override the default values
defined in the jpm.xml file (located in your JIRA application
installation directory). See Advanced JIRA configuration for more
information.
In new JIRA installations, this file may not initially exist and if
so, will need to be created manually. See Making changes to the
jira-config.properties file for more information. This file is
typically present in JIRA installations upgraded from version 4.3 or
earlier, whose advanced configuration options had been customized
(from their default values).
plugins/
This is the directory where plugins built on Atlassian's Plugin
Framework 2 (i.e. 'Plugins 2' plugins) are stored. If you are
installing a new 'Plugins 2' plugin, you will need to deploy it into
this directory under the installed-plugins sub-directory.
'Plugins 1' plugins should be stored in the JIRA application
installation directory.
This directory is created on JIRA startup, if it does not exist
already.
I've an OpenShift installation.
From the installation environment, I can reach it via
https://console.pat.net.priv:8443
the machines name is "pat".
If I try to reach the openshift installation from a foreign machine
the side can't be reached.
If I call https://pat.net.priv:8443 I'll be rerouted to https://console.pat.net.priv:8443.
Here the problem starts;
https://pat.net.priv:8443/login?....
opens the login but returns to an
https://console.pat.net.priv:8443/console/oauth?code=...
link. The Problem is https://console.pat. ... can't be resolved?
Can someone help me? I need detailed instructions on how to do.
I have issues with my app: when it goes in the "idle" state and then goes back to the "started" state, it messes up one of my cartridges. Basically a PID file is not removed, so I have to delete it manually before restarting the cartridge. This PID file is removed when stopping the cartridge manually.
So I am wondering: what happens when the app goes in the "idle" state? Is it equivalent to stopping the app manually? Which cartridge scripts are executed when that happens?
Thanks for your help
You may try the web console restart command.
But mostly the force restart from the rhc command tools renders better results.
http://www.howtech.ga
I am trying to use the EC2 plugin from jenkins to launch a slave agaent instance on AWS EC2. However I want to be able to specify my security group and as of right now it forces me to choose default. Does anyone know a workaround for this?
I looked on git and apparently there was a pull request for this feature. I'm not very familiar with it but it did say it was closed so does that mean it never got commited?
Thanks in advance!
It's not tested or anything, but my fork has security groups as of today.
https://github.com/jmoses/ec2-plugin
There's also no downloadable .hpi in the repo, so you'd have to build it. I'll probably upload one at some point, or drop me a message and I can shoot you the one I've got. Work in progress.