What is the great motivation behind integrating Redmine with a source control repository ? If it is only for monitoring reason, developers already have access to repository and they can do whatever they want diff, history with their IDE. For other people do they really need? I'm afraid, I can't see the real reason. Can you please help me to see ?
When you fix a bug that exists in Redmine's issue tracker, you can refer to the issue id in the commit message and Redmine will automatically associate the commit with the issue (or even close the issue).
This saves you the double work of referring the issue in the commit message and closing the issue in Redmine.
By the way, this is not Redmine-specific - you can do it with most bug trackers that offer source control integration.
I don't remember the exact syntax in Redmine right now, but most of the time, the syntax is something like:
fixes #123
...which would cause Redmine to automatically close issue #123, and create a link from the issue to the commit (and vice-versa).
Related
The end result:
After publishing an item, all versions will be visible in the WEB DB, instead of the default behaviour of only having the latest item version.
I'm using Sitecore 8.2.170407
After reading this article, I tried to do several things:
Remove both RemoveOtherVersions and PublishTestingVersions processors by doing a <patch:delete />. That did not work
Add my own patch file, which inherits Sitecore.Publishing.Pipelines.PublishVersion.Processors.RemoveOtherVersions and hides/overrides the base Process method. The new method will do nothing.
Image of patch class and Image of patch config
That didn't work either.
Tried removing the whole <publishVersion> pipeline, but that gave an exception when trying to publish an item.
I've not been able to find a solutions anywhere else. I know a similar question has been asked here, but that was in Sitecore 6
Have any of you been in the same situation before? How did you solve the issue?
If you need more information, please let me know.
Thanks in advance
You can't.
The linked answer you provide is still valid. Sitecore "web" database (any database which is a publishing target) stores one and only one version. To modify this, you're going to need to reinvent your own publishing process.
Based on your clarification, it seems what you want to use is standard Sitecore versioning with specified publish start dates to put up a particular version.
All of the versions would live in your master database, and you would regularly run publishes through the publishing agent or some other means in order to send the appropriate version to the web database on the correct date.
Your authors can preview what the page would look like on a particular date using the date picker in the preview mode.
My question is about using dynamics 365 JavaScript validator on a Managed solution?
will it work on a Managed solution?
I have used the JavaScript Validator and it only shows a log of all the API calls that will be deprecated along with their web resource name and line the code is on.
With this knowledge you can just run it on the managed solution and check
https://www.xrmtoolbox.com/plugins/XrmToolBox.Dynamics365V9JavascriptValidator/
I hate to say that it probably will not matter as you would not be able to update the Managed Solution if it failed anyway. Since Managed Solutions uninstall cleanly, I would:
1.) Create a test environment at trials.dynamics.com then install the Solution.
2.) Test the Solution to see if it performs appropriately.
3.) Attempt to uninstall the Solution cleanly.
You should have your answer there.
Additionally, check with the Publisher to see if there are any updates. Hope that helps.
Is it possible to make redmine intercept the commit messages and act, like on assembla, if I commit and write fix #12 than issue 12 status changes to fix.
Any plugin for this behavior?
No plugin needed, it works the same way as it works for SVN or mercurial.
However, in order for redmine to pick up the new commit messages, you either have to open the repository page in redmine, or schedule a task to do so regularly.
as #afarazit said, plus you probably want the issues to update live in Redmine without needing to manually enter in the Repository tab to force the refresh.
That can be done by using this server-side post-receive hook:
#!/bin/bash
_apikey=YOUR_API_KEY
_projectid=YOUR_PROJECT_ID
curl -k "http://REDMINE_SERVER_URL/sys/fetch_changesets?key=$_apikey&i
d=$_projectid"&
Redmine has this functionality by default. You can use refs, references, IssueID for references and fixes, closes for fixing issues. You can also add your own keywords to be parsed from redmine and do stuff to your issues.
You can find more info on documentation
We are planning to move over our project management to Redmine and also our Git repositories from Github to Redmine. Are there any potential hazards or drawbacks we should consider? We are a growing team. We will be using these across cross functional teams. Members will range from 20 to 60 or more (in all teams).
I can only suggest you look at this list of issues on the Redmine project's site - naturally, they use Redmine to track them.
We have been using Redmine for a year now (although not with git), we have about 15 users, and have not experienced any issues with it.
If you are concerned about stability, it might be an idea to use an older version with no known serious bugs, rather than the latest version.
I have customized Redmine for our team here. It is a great piece of Software with some really useful and agile-focused plug-ins. We use Redmine Backlogs, stuff-to-do plugins which are great. I was wondering if anyone was successful in setting multiple repositories in a single project? I know that I can create a sub-project and set up a different repo. But there could be cases where there is a need to have more than one repos in the 'Repository' tab of Redmine(For example code might be in development environment initially and then moved to staging and production and so need for two repos for a project) and also to get the issues associated with the commit messages. That is one of the drawbacks for some people.
This could get mandatory if you have a pre-commit hook to refer to issue numbers.
How to remove my jar from clojars? I don't want to mess up public group namespace. I want to move myproject/myproject to org.clojars.qertoip/myproject.
Open a ticket in Clojars' issue tracker on github. If you need it done privately (perhaps for security reasons) email the server caretakers.
If you would like to discuss the policy or help implement an alternative mechanism see this github issue.
There are more details in the Clojars About wiki page
I had the same trouble, when I asked on the irc channel ato told me that there is no option for removing jars cause someone may be already depending on them, what he told me was that he may remove it manually if i wanted to.
I don't think there's a mechanism for doing this yourself. Consider asking Clojars admin Alex Osborne (ato on github) to do it for you.
You might not be able to remove a jar, it however is possible to overwrite an existing jar by redeploying the same version