I have problem with Jira Cloud and Bitbacket. When I make smart commit - Jira only synchronize data commits with 60 min interval. Can I change this setting in Jira Cloud?
May be anybody had such problem? Thank You!
Seems that in cloud instances web hook from Bitbucket is responsible to trigger sync. I believe Benjamin Morgan replied to similar questions in Atlassian issue tracking. I would recommend you to take a look at it (here).
However, since Atlassian Cloud instances change regularly it's difficult to verify if it's still a valid configuration or not.
Related
Never mind the rationale, I have a case where a build needs to run every 5 minutes. On-premise installation does not support schedules in the YAML.
So, how do we do it? I can probably use the REST Api, but that sucks, because it seems either I create a one-off script or a script for very simple type of schedules. Building a reusable solution, that could be used in general for other builds seems to be involved. So, instead of concentrating on my business I need to go sideways and cover for the deficiencies of the on-premise version of Azure DevOps.
I wonder if there is a better way.
Understand your concern. However, this is not supported at present with on-premise TFS sever.
The UI for defining time-based build triggers isn't flexible enough. It can only support fixed times on days of the week.
Just as you have pointed out in the comment, we have a need to run a build every 5 minutes which requires us to create 288 schedules which is tedious.
Actually, this has already been a user voice.
Scheduled builds - More flexible timing configuration
https://developercommunity.visualstudio.com/idea/365630/scheduled-builds-more-flexible-timing-configuratio.html
Multiple persons commented and echoed. After go through the marketplace, haven't found a pretty appropriate workaround. Sorry for any inconvenience. You could monitor the status of above user voice.
We recently added "Publish To Apple News" plug-in to our Word Press and getting "Date_Not_Recent" error. After talking to the developers and checking their support pages, it looks like it is a a time zone issue between the WP server (Oregon, US with UTC timezone) and Apple News Publisher (which till this moment Apple can't tell me where it is located, i assume California, but who knows for sure?)
Solution, is to sync those time zones together. My questions:
1- Anyone had any issues rezoning their aws servers?
2- If you had this issue before, what did you do?
I am just trying not fix one thing and break 10 other things in return. just being cautions. We all know that Murphy's law roles in IT.
Thanks in advance
We figured it out. it was an NTP issue.
We host on AWS, and the time sync packages (NTP) were a little bit out of sync, so we deleted them and installed chrony instead and that worked.
For anyone who is interested, here are the instructions (under configuring the Amazon time sync services):
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html
Does anyone know of a good time tracking add-on for Bitbucket?
Something where I can put time manually and associated cost per hour, which would then give me the total?
You can use TMetric time tracker addon for Chrome to use it in Bitbucket.
There is a small tutorial of how to start to use it https://tmetric.com/integrations/asana-time-tracking/
There is no page dedicated to Bitbucket time tracking but it is pretty the same like with Asana.
is it possible to configure a hard limit on the number of open changes for a given project in Gerrit?
When too many changes accumulate, rebasing them becomes an issue, especially when every rebase triggers a Jenkins job which takes some time to complete.
Hence I am looking for a way to force a limit on the open changes, so that Gerrit rejects new changes when too many are still open.
Thanks for help in advance.
You can start with git hooks. You can then use gerrit's ssh api or directly talk to gerrit's database to query outstanding gerrits.
Alternatively, consider using polling in jenkins instead of triggering a build on every change.
Like every commit has a reason and purpose, I think each deploy has a purpose and reason. Source code commits have a comment. But deploying doesn't have any.
How do I record a reason and purpose for each deploy automatically?
I need to keep a record of:
Who deployed to where and what time.
Why deployed? Bug fixes? Feature update? Emergency fix not on iteration plan?
Which git or svn ref was used?
Have anybody felt the need for this kind of system? How do you feel about my approach?
How can I achieve my goal? I'm currently using Capistrano for deployment.
A bounty added. I'd like to hear more stories from different developers who are doing "continuous deployment".
I found two services that do deploy tracking:
Codebase
Hoptoad
Webistrano - https://github.com/peritor/webistrano/wiki - is a web interface to capistrano, that also tracks who's deployed what and when, so that could be worth investigating.
My current project uses a modified version of the apinsein's git-deployment recipe, which (when you tell cap to do a deploy) will tag current HEAD with a Git tag (which gives you all the benefits of normal Git commits).
I've built a web service for this exact problem, http://deploytracking.com, it hooks into capistrano and records the time, user, branch, ref, environment and repo that was involved in the deployment.
Strano - The Github backed Capistrano deployment management UI.
Regarding continuous deployment, I also submitted pull request there, which Introduce automatic deployments for GitHub projects, for now it simply triggers deploy task when somebody push to the master branch.
I don't know if it is still relevant but I would like to come up with a different solution. I am building a new deployment tool that does just what you are looking for.
I do not intend to spam my stuff here but since I am building something that could help you...
Anyway, have a look here https://alessiosantocs.github.io/Captain. I'm gathering feedback so if you have any please let me know.
Update
As suggested, I'm giving an explanation :)
I have also felt this need. I work in a digital startup and we're constantly deploying stuff 5 days a week on different Ruby on Rails application with Capistrano.
What we noticed was that for every single deployment, we should have done several things:
Keep track of which pull requests and commits went online that exact moment
Give some sort of a name to the deploy so we could recognize it
Alert our team members so that everyone could have been on the same page (without asking us of deployment's news)
Keep track of every deployments for future bugs and errors we might find at some point in time (which happened often)
So for this reason we started developing this custom solution that would integrate with Capistrano and our SCM (bitbucket) and keep track of every change we made to our master branch. This is what it does right now.
We are currently tracking deployment environment, repo source, deployment branch and revision. Mainly we manage pull requests, because we found that pull requests, better than commits, did solve an organizational issue in our team (it was difficult to approve other team member's code without a rigid system like PRs)
I would like to explain more about Captain and about our personal dev management strategy with you guys if you want.
Thanks #thirumalaimurugan for asking for clarification!
Update 2
We tried git tagging too. It was good and fun at the beginning but we couldn't manage them very well.
A tag is basically a bookmark to a specific revision. So we're talking about commits. A tag keeps no track of pull requests. It was quite a mess for us.
I don't think they're bad at what you're trying to achieve, but I think there must be some other solutions that could fit exactly your (and our too) problem.