I would like to configure SonarQube Leak Period to match our sprints (14 days). We don't release after each sprint, and our branch is always "develop" so I can't key off of a release.
I know that I can configure X number of days, but I don't want a rolling account over a 14 day period... I would like it to do the delta by comparing each of the 14 days to Day 1. So, Day 2 <> Day 1, Day 3 <> Day 1, etc. Then on the 15th day it would reset for the start of the new sprint.
How can I configure SonarQube to always start the leak period with the start of a new sprint?
Because you don't want a rolling 14-day period, you'll have to manually re-configure to the start date of the new sprint every 2 weeks.
Alternately, you could jigger your versions to something like
3.14-sprintAlpha
3.14-sprintBeta
...
And use the previous_version leak period setting.
Related
In Jira there is a Time Report where you could see how many hours spend on the task an employee, and for month report you could see all tasks together and total time spent day by day on the task and total sepent time to be able to report to the customer, about how much time spent each employee.
I could not find normal documentation for such feature, I am expected to get help, if there is such feature, how to use it and setup.
I'm not sure if that title makes much sense.
Right now, I have a fair amount of data coming in through logstash - about 7-10GB/day, and it all needs to stick around for 60 days. I currently write it to an index ("index-20220718") for example, based on the current date, and just delete any index older than 60 days. That's easy.
But things are changing.
Soon I'm going to have data coming in that will have different, dynamic expiration dates. Some records need to stick around 15 days, some 30 days, some 365 days, some 3650 days. The retention period is in a field that's in the data.
So what's the best way to index this? I thought of using date math, adding the number of days in the retention field to the current date, and storing it in an index like "index-20220802" if it had a 30 day retention period, and then deleting any index that's dated before today.
Is this the best way to do it? Is it going to complicate searches? I'm just the sysadmin setting up the basic logstash/ES configuration - I'm not any sort of expert on ES or programming.
If a customer changes the retention period for their account, I guess we'd have to go through and re-index everyone of their documents?
I feel like I must be missing other problems with this method too.
Is there a better way to do this that I'm just not seeing?
Thanks-
I'm new to Heroku and planning to upload all my applications there until i made some research about package pricing and found out that free apps get around 550-1000 dyno hours per month and for standard package 25$-50$ per dyno per month, now here lies the question.
Does this mean that standard Package X1 for instance if I consumed 1000 dyno hours per month i will billed 25($/dyno) x 1000 dyno = 25,000$ per month?.
Every Dyno type has a different price which is what you pay every month, for example $25 for standard-1x. That's what you are billed every month (no more).
The hours come in place when you select a Free Dyno:
the first 550 hrs are free, after that the Dyno stops working (next month you get the same quota and the Dyno can restart)
you can extend to 1000 (free) hrs if you register a valid Credit Card
Can you please help me with, what can be used to for scheduling an oozie coordinator job to execute on first Monday of every month.
I know we have a frequency parameter that can be set as ${coord:months(1)} . But this will not allow me to schedule the jobs on a particular day of a particular week of a month. Hope I am not complicating the question here.
Any help is strongly appreciated.
Thanks,
Syed
You unfortunately cannot schedule in the specific manner you are looking for. As you already note, you can run on a monthly basis - i.e. the 5th day of each month, but you are not be able to control the Day of the Week other than for the first materialization.
A possible work around this would be to run your coordinator on a weekly basis, to materialize on the Monday and then have a custom Java Action as your first step in the workflow that will throw an exception if it's not the first day of the month.
A downside of this approach is that you'll see 4 or so failures per month in the job list for the coordinator, but at least it will give you the behaviour you're looking for.
I have a PLSQL program with three cursors. This program should run as a job.
The job should run on any day between 1st and 5th of every month. And also between 25th and last day of every month. How to write a logic to run this program?
I would set a database job to run every day and then make a simple if clause at the start of the program to check if it's valid day to run the rest of the code.
Check out the DBMS_SCHEDULER routines.
The new version (v3) of Oracle's SQL Developer has a nice GUI for setting up schedules