I want to start using Redmine with Gitlab for issue tracking.
Is there a way to update the gitlab configuration (gitlab.yml) with the redmine urls and start using both applications without having to bundle Gitlab again?
Not exactly.
There is a Redmine plugin which does the opposite: "Gitlab Merge Request"
This plugin allow you to add a "New merge request" link on redmine issue.
Gitlab merge request form will be filled based on project configuration
And there is a (closed) feature request issue 97 asking for using Redmine is recommended for Issue management (again the opposite of what you are asking for)
However, this feedback request is closer:
I currently use Redmine for my issues in oreder to do time-tracking, gantt, versions, guest access.
I think it would be cool to allow setup for Redmine issues to be synced into Gitlab and possibly vice versa.
You can now link Redmine issues from GitLab: see gitlab.yml.example.
## External issues trackers
issues_tracker:
# redmine:
# title: "Redmine"
# ## If not nil, link 'Issues' on project page will be replaced with this
# ## Use placeholders:
# ## :project_id - GitLab project identifier
# ## :issues_tracker_id - Project Name or Id in external issue tracker
# project_url: "http://redmine.sample/projects/:issues_tracker_id"
So it doesn't replace Redmine issue management with GitLab's, but it helps keeping the two in sync.
Related
So here's my situation...I have two React apps that need to talk to the same Cognito User Pool. I've been able to accomplish this by copying the aws-exports.js file from the first app to the second app I created (not sure if this is something I should be doing or not but it is working). The issue I am having however is when I run an Admin Query on the second app (to say list users in the Cognito User Pool) I get a 403 (Forbidden) error. Has anyone ever run into this before? Googling all day has not helped me so I figured I would ask.
You'll need "multi-frontend" solution:
https://docs.amplify.aws/cli/teams/multi-frontend
I'll give you some useful infos for this:
Open the Amplify Console and there the "first" app (wheres the backend was created).
Go to the first app's "backend" section
Select "Backend environments" tab
Search for "Edit backend" box and this text: "To continue working on the backend, install the Amplify CLI and make updates by running the command below from the root of your project folder"
copy that command, and paste/run in second app's root.
Beware!
do not modify (and push) the backend from the second application.
if you use git branch based environment you must always switch the env AND the branch parallel. Do not pull the "master" backend for your "dev" env.
try to avoid modifing on amplify console if you modify things with amplify cli. Those things cannot be syncronized... :(
If you store multiple apps in a git monorepo:
https://docs.amplify.aws/cli/usage/monorepo
My organization is using Ember addons to develop a set of shared components between our applications. Let's call this repository app-components. Currently the components application's primary responsibility is to distribute CSS, fonts and images.
We are also building a living styleguide that will ingest our shared components and present them in a neutral way for developers to reference. Let's call this repository app-styleguide. Our goal is to deploy app-styleguide using ember-deploy to deploy this solution to Github Pages. The url follows this pattern:
https://organization.github.io/app-styleguide/
When the app-styleguide application makes it to the gh-pages branch and is served as a webpage, all of the fonts and images being delivered by app-components are giving us a 404. I have referenced a handful of different solutions to this problem, but I keep coming across the same solutions that we have tried.
I have tried using the following two ember addons that automate the deploy to github pages:
https://github.com/poetic/ember-cli-github-pages
https://www.npmjs.com/package/ember-cli-deploy-gh-pages
In the end we went with a vanilla ember-cli-deploy solution, as those two addons are quite old...
I have followed the instructions here to add rootUrl andlocationTypeproperties to ourenvironment.js` file, which has not worked:
https://github.com/ember-cli/ember-cli/issues/398
Our environment.js file looks like this:
if (environment === 'production') {
ENV.rootURL = '/app-styleguide';
ENV.locationType = 'hash';
}
And our requests continue to not add app-styleguide to the request URL's for assets coming from the Addon. Here is an example of a failed request from the Chrome DevTools Network tab:
Request URL:https://organization.github.io/assets/images/thumbnail-icons/person.svg
Request Method:GET
Status Code:404 Not Found
As you can see, app-styleguide is not added to the request.
Any help is greatly appreciated!
I was able to receive some help over on the Ember Slack Community
(special thanks to #alexspeller). It turns out I needed to update a couple of settings in the fingerprinting of assets.
Using the included broccoli-asset-rev library I had to modify my ember-cli-build.js to include the following:
var app = new EmberApp(defaults, {
fingerprint: {
extensions: ['js', 'css', 'png', 'jpg', 'gif', 'map', 'svg', 'ttf', 'woff'],
prepend: '/app-styleguide/'
}
});
I needed to update the options to account for SVG, TTF, & WOFF, as well as the proper prepended url segment.
You can read about the functionality here:
https://ember-cli.com/asset-compilation#fingerprinting-and-cdn-urls
Available options:
https://github.com/cibernox/broccoli-asset-rev?files=1#options
In Redmine, I can use edit button to edit everything of an issue. However, in daily work, the most frequent actions other than update the issue status are "resolve an issue", "close an issue" and sometimes, "re-activate an issue". When resolving an issue, the "assign to" field will be updated to the opener and issue status to "resolved".
I used to add an js to the issue details page to do similar work but it will be gone after redmine upgrading. What's the correct way to do accomplish this task?
Thanks
If you want your custom code to be preserved while doing Redmine upgrades, there are few options:
make it a plugin
install Redmine via svn or git, and perform code updates, it should preserve code that you wrote, and automatically merge rest of
the code
run your custom javascript via greasemonkey or tampermonkey
I would like to get the build badge image on my project from Gitlab CI. I know the url (documentation) :
http://example.gitlab.com/namespace/project/badges/branch/build.svg
But my project is a private project, and the link require authentification and I don't know how to be authenticated with this url.
Thank you for your help.
Your project/repository's README.md should be able to show your badge as it's already in an authenticated session with your/the Gitlab server. If your trying to show the badge on a different, non-Gitlab page on the same server, you could symlink the build.svg to a location in your www root and ensure that your other webserver to follow symlinks.
After upgrading Redmine to 1.2 I can not save email notification and language settings on "My account" page.
I ran rake migrate, but that did not helped.
What can cause that problem and is there any way to fix it?
Thanks a lot.
If you want to save your configuration, you can simply save the "email.yml" file (for email configuration) and "database.yml" (for database configuration).
These files are situated on :
<your_redmine_installation>/configuration/